It looks like Avalon has been steadily deprecating interfaces that James
has been depending on.  Now James is broken.

   http://jakarta.apache.org/builds/gump/2001-02-11/james.html

Who wants to volunteer to look into it?

Standard reason: if one wants to deploy a server solution involving
multiple Apache Jakarta subprojects, each of which depend on different
point in time snapshots of Avalon, which version of the avalonapi.jar
should one put into the classpath first?

- Sam Ruby

P.S.  Kudos to the Avalon team for deprecating interfaces.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to