Sorry I'm getting back into this late. That bloody email virus had our mail
server off line for a while.
The intent of 3.2.2 is to release bug fixes for existing functionality.
Since Tomcat 3.2.1 doesn't support Apache 2.0 then it is completely valid
for 3.2.2 not to support it. Adding new functionality at this point runs
too high of a risk of creating unexpected consequences.
> -----Original Message-----
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> Sent: Monday, February 12, 2001 4:35 PM
> To: [EMAIL PROTECTED]
> Subject: Re: mod_jk TC 3.2.2 != TC 3.3
>
>
> GOMEZ Henri wrote:
>
> > >Agreed, i'm reluctant too to adding features to TC3.2, only bugfixes on
> > >TC3.2.. so any bug fixed on TC3.3 that must be done , no more nor less
> > >than that.. and it's a big piece of work only with maintenance
> > >of actual
> > >code...
> >
> > If we didn't upgrade mod_jk, Tomcat 3.2.x couldn't be use with
> Apache 2.0.
> > Apache 2.0 will be only for TC 3.3 users....
> >
>
> That would be entirely consistent with our philosophy that Tomcat 3.2.2
> contains only bug fixes, not new features.
>
> Craig McClanahan
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
