Sam Ruby wrote:
>
> Charles Benett wrote:
> >
> > Strange, it wasn't a couple of days ago. And deprecating
> > interfaces shouldn't break a build.
>
> Eventually, a change was made that was not backwards compatible.
>
> > When i get a chance. Can you be more specific as to what
> > is broken?
>
> Thanks! Sure:
>
> http://jakarta.apache.org/builds/gump/2001-02-12/jakarta-james.html
>
> > I'm not sure you can yet, because the packages keep changing.
>
> Then it it irresponsible to be depending on these packages just yet. It
> looks like Tomcat 4.0 is coming to that conclusion. (Integration with
> Avalon with continue in Tomcat 4.1)
>
> Meanwhile, I would suggest that it is important that those projects that
> wish to remain on the bleading edge keep up.
>
> > BTW, what are gump and tinderbox? Do they have any web docs?
>
> Not yet.
>
> I've been concerned about version compatibility issues for quite some time.
> What you see on that web page is an automated attempt to build each project
> with the latest versions of each of its dependencies.
>
> Code for this is checked into jakarta-alexandria, in a proposal/gump
> directory. Discussion of the implementation should go to
> [EMAIL PROTECTED]
Hmm. Good idea, but I can't see it working for james, yet. There aren't
enough active james developers to keep up with daily changes in avalon.
James runs fine with the last release of Avalon, 3.1a1.
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
