Aaron Mulder wrote:
> 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.
>
That would be my preference.
I was thinking, it ought to be possible to create a
process/module/project/something that takes the output bits of a Tomcat 4.0 binary
distribution, and the output bits of an Avalon release, and combine them into an
Avalonized installation of Tomcat 4.0. This is not a lot different than what
Henri does when he creates RPMs -- it is done external to the standard Tomcat
build process.
If we want to go this direction, what modifications does "making any Tomcat
changes necessary to support the Avalon patch" include? (I haven't had a chance
to look at Jason's proposal in detail yet.)
>
> Aaron
>
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
