> It's always going to be the case that the Avalon and Tomcat releases
> don't sync up perfectly. How would you feel about making any Tomcat
> changes necessary to support the Avalon patch, but maintaining the
> Avalon block itself outside of the main Tomcat 4.0 module? That way the
> Avalon support could be updated independently for new releases of Avalon
> *or* Tomcat.
Actually, I was thinking starting a modules subprojects for things like that
in 4.1.
Right now, the version number for Avalon is 3.1 alpha 1.
It's common sense that we will need to keep that component in sync with
Avalon, but at least we can indicate users to use a specific stable version
until we update, and the amount of updates needed should be reasonable (I
hope).
Does it make sense ?
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
