At Avalon we are debating over Jar Naming Conventions and I think the same is
appliable to JAMES: you should have two different jars, one for the generic
API ( I suggest mailet.jar or - Java Apache Mail Servlet Interfaces -
jamsi.jar) and one for the server implementation (I suggest james.jar as this
is the codename of the project).
This way you distinct between the generic API and it's implementation, both
developed under the ASF umbrella but the first should be ruled by the Java
Apache group and the second will be a container for it's implementations, just
in the same way it's done for servlet interfaces.
In addition I suggest to split package names into
org.apache.james -> Mailet container
org.apache.mailet -> Mailet interfaces
allowing easier management and more stability to the interfaces package when
it reaches a good revision.
This approach is more in synch to the one used by Sun and we have to admit
it's working well to separate them.
Roberto
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
