RE: mod_jk TC 3.2.2 != TC 3.3 = was RE: [PROPOSAL] Tomcat 3.2.2 Rele ase Plan

2001-02-12 Thread GOMEZ Henri
: Friday, February 09, 2001 12:15 PM To: [EMAIL PROTECTED] Cc: Dan Milstein; Keith Wannamaker Subject: mod_jk TC 3.2.2 != TC 3.3 = was RE: [PROPOSAL] Tomcat 3.2.2 Rele ase Plan While looking updating TC 3.2.2 with mod_jk for Apache 2.0 I notice that mod_jk from TC 3.2.2 and 3.3 are still differents I

RE: mod_jk TC 3.2.2 != TC 3.3 = was RE: [PROPOSAL] Tomcat 3.2.2 Rele ase Plan

2001-02-12 Thread GOMEZ Henri
No, it was decided to not start changing the 3.2.x tree. If people want the fixes, they can always upgrade. Sorry but adding bug corrections is not changing the tree. People may also want to use the mod_jk stuff with Apache 2.0. If we didn't back port corrections on mod_jk / ajp from 3.3 to

Re: mod_jk TC 3.2.2 != TC 3.3

2001-02-12 Thread Dan Milstein
PROTECTED] Cc: Dan Milstein; Keith Wannamaker Subject: mod_jk TC 3.2.2 != TC 3.3 = was RE: [PROPOSAL] Tomcat 3.2.2 Rele ase Plan While looking updating TC 3.2.2 with mod_jk for Apache 2.0 I notice that mod_jk from TC 3.2.2 and 3.3 are still differents I attached a list of diff without

RE: mod_jk TC 3.2.2 != TC 3.3

2001-02-12 Thread Ignacio J. Ortega
I don't particularly want to multiply the codebases we support (and the differences between them), but, especially since we're nearing a 3.3 release, my instinct is to vote against applying all the 3.3 work to the 3.2 branch. Agreed, i'm reluctant too to adding features to TC3.2, only

RE: mod_jk TC 3.2.2 != TC 3.3

2001-02-12 Thread GOMEZ Henri
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

Re: mod_jk TC 3.2.2 != TC 3.3

2001-02-12 Thread Craig R. McClanahan
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

RE: mod_jk TC 3.2.2 != TC 3.3

2001-02-12 Thread Marc Saegesser
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

RE: mod_jk TC 3.2.2 != TC 3.3

2001-02-12 Thread GOMEZ Henri
Sorry I'm getting back into this late. That bloody email virus had our mail server off line for a while. I seems to be an attack against the majority of Apache list (xml / jakarta). The intent of 3.2.2 is to release bug fixes for existing functionality. Since Tomcat 3.2.1 doesn't support

Re: mod_jk TC 3.2.2 != TC 3.3

2001-02-12 Thread Pier P. Fumagalli
Craig R. McClanahan [EMAIL PROTECTED] wrote: 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...

Re: mod_jk TC 3.2.2 != TC 3.3

2001-02-12 Thread Pier P. Fumagalli
GOMEZ Henri [EMAIL PROTECTED] wrote: Sorry I'm getting back into this late. That bloody email virus had our mail server off line for a while. I seems to be an attack against the majority of Apache list (xml / jakarta). And the majority of the world itself

mod_jk TC 3.2.2 != TC 3.3 = was RE: [PROPOSAL] Tomcat 3.2.2 Release Plan

2001-02-09 Thread GOMEZ Henri
While looking updating TC 3.2.2 with mod_jk for Apache 2.0 I notice that mod_jk from TC 3.2.2 and 3.3 are still differents I attached a list of diff without the version which are also different in each files. I propose that the whole TC 3.3 mod_jk native code (ap1.3, ap2.0 and common) are