>�From: Roberto Lo Giacco <[EMAIL PROTECTED]>
>�Date: Tue Aug 29 09:30:31 EDT 2000
>
> 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
YES! YES! YES! I love it! This is exactly what I was trying to do in separating the
API. In fact, I even renamed org.apache.mail to org.apache.mailet as per your
suggestion. I was then going to have all the avalon/james neutral code in the
mailet.jar. This is perfect! The problem before this separation was that the mailet
API was tied directly to james and avalong. Assuming nobody starts throwing rocks at
my API separation, I'll commit my changes later this week and have JAMES run off of
the 2 separate jars. (unless we're still in active discussions of course)
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
