Robert Burrell Donkin ha scritto:
ATM http://svn.apache.org/repos/asf/james/mailet/api/trunk/ contains
both the API and utility classes. the 2.3.1 release has mailet and
mailet-api jars. IMHO it would make sense to split the mailet-api
product into a similar way: mailet-api (containing just the API) and
mailet-base (containing the utility classes currently in mailet/api.
opinions?
IIRC the separation in mailet and mailet-api jar seems a little random ;-)
Mailet class is in mailet-api.jar, Matcher is in the mailet.jar !?
So Matcher, MatcherConfig and MailetException are not in mailet-api,
while maybe they should be.
ATM there are really so many classes that I would be tempted in
releasing a single jar, on the other hand I know that we'll need an
"utility" library to be able to move some more mailet from server to a
mailet library, so maybe "base" will be able to host them too.
In the end.. +1
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]