Grant,
Thanks for the update on Avalon! I actually spent some time last week working through
a new version of the server mail API that will completely separate it from Avalon (not
the JAMES implementation itself... just the mailets and matchers). Then as JAMES
mutates to follow Avalon's progress, users won't be as affected because custom mailets
and matchers and their configuration won't be tied to the Avalon version.
I've got most of the new API drawn up at home, and later this week I hope to send it
around and apply patches as needed. Most changes aren't significant as it's just
blocking the mailets from seeing anything Avalon specific and providing standardized
methods to get this information or that function... behavior doesn't really change.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
>�From: Grant Sparks <[EMAIL PROTECTED]>
>�To: Java Apache Mail Server <[EMAIL PROTECTED]>
>�Subject: RE: Avalon2.1 and James.1B1
>�Date: Tue Aug 15 04:40:09 EDT 2000
>
> We are also working on bringing together the latest distributed versions of
> avalon, james, tomcat and jetspeed. Right now I have a build.xml that will
> compile these and the latest turbine cocoon etc, but it still comes down to
> about 70 or so errors when building james against this. If we start the
> build directly from the current CVS, its even messier.
>
> These are mainly due to the following causes; (PLEASE CORRECT WHERE WRONG -
> I've put this together by looking around over the past few days)
> - There are currently 3 major operational versions of avalon. avalon2.1-dev
> (the distribution on their web site), 2.2 (which james uses), and the latest
> CVS sources which have now removed the Component Manager (or are working
> towards this) to be replaced with JNDI.
> - There also appears to be some migration towards org.apache.java of objects
> that used to be part of other sub projects (like avalon). This has made the
> proper contents of the org.apache.java namespace a little fuzzy to me. Also
> there have been class name changes (SimpleContext->DefaultContext) that are
> yet to be fixed throughout the code base.
> - Some sub projects are still in transition towards tomcat (Servlet 2.2 API)
> leaving a few uncomfortable dependencies. Also the competing XML
> implementations just confuses me.
>
> I figure that if a few people worked on it for a few days they'd probably be
> able to bring all of the above projects together, but I decided to get my
> team working on their own stuff instead and just wait it out until all the
> contributors finally check in the changes they've been working on.
>
> I think a unified build of the majority of the java.apache projects together
> is achievable in the near term. Please let me know if you are working on
> this. I'll put it all up on a webpage if there is interest.
>
> Cheers,
> Grant.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
