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.
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of [EMAIL PROTECTED]
> Sent: Sunday, August 13, 2000 9:24 PM
> To: Java Apache Mail Server
> Subject: Re: Avalon2.1 and James.1B1
>
>
> On Sun, 13 Aug 2000, Harmeet Bedi wrote:
>
> > I downloaded James.1B1 and Avalon 2.1. Could not get both to
> work togther.
> > After that got the latest James Snapshot from CVS. It still did not
> > interoperate. After some work/code changes to James code base,
> got the thing
> > going.
> >
> > Is Avalon2.1 compatibity an aim ?
> > Would the work I have done, be useful to someone or the James
> developers ?
>
> Not sure. Avalon has changed *a lot* since 2.1 and will be
> changing even more so for the moment James will be utilising
> old Avalon stuff. I am not sure if it is useful to update
> James to Avalon 2.1 (BTW what changes were needed ???) but
> it could be. If the diffs are small enough post them to this
> list otherwise chuck them on a web page somewhere.
>
> Cheers,
>
> Pete
>
> *--------------------------------------------------*
> | Latrobe University, | |
> | Bundoora, Australia | Does the name 'Pavlov' |
> | Office: PW220 | ring a bell ? |
> | Ex: 2503 | |
> *--------------------------------------------------*
>
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
