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.
Aaron
Remy Maucherat wrote:
> I'm -1 on applying the Avalon patch in the 4.0 tree.
> The rationale is :
> - Avalon isn't ready yet. It's still in alpha stage, and I fear there may be
> API changes in the pipeline.
> - TC 4.0 should be out before Avalon. If Avalon 3.1 evolves *after* TC 4.0
> is released, this would break the wrapper included in TC 4.0 and make it
> incompatible with the Avalon 3.1 production release, which would more or
> less force us to do a TC maintenance release.
>
> For these reasons, I'd like to see an official Avalon wrapper introduced in
> Tomcat 4.1, but not in Tomcat 4.0.
> I also propose to remove the current Avalon wrapper from the Tomcat 4.0
> repository, to avoid the maintenance related issues.
>
> The 4.1 repository should be recreated very soon, since TC 4.0 has gone back
> into feature freeze mode (but we want to fix the sealing violation problems
> reported by many people before).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
