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

[GOMEZ Henri <hg...@slib.fr>]

I didn't received replies to my post on mod_jk differences 
between TC 3.3 and TC 3.2.2.

I've proposed to copy all the mod_jk native code from TC 3.3 to
TC 3.2.2 before release. They were many bugs fixed in both
native and java parts, and it will be a pitty to let the release
goes without that fixes. 

I think that both Dan and Keith have each time back ported 
the Java corrections in tomcat_32 but it must be validated with them.

Another interest, is that mod_jk from TC 3.3 works with the latest 
Apache 2.0.

>-----Original Message-----
>From: GOMEZ Henri [mailto:hgomez@slib.fr]
>Sent: Friday, February 09, 2001 12:15 PM
>To: tomcat-dev@jakarta.apache.org
>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 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 reimported in TC 3.2.2 to avoid confusion and
>mistake, and let us be sure we at the same level.
>
>What about ?
>Who could do that ?
>

Re: mod_jk TC 3.2.2 != TC 3.3

[Dan Milstein <da...@shore.net>]

[I meant to send this to the list on Sunday, but apparently sent it only to
Henri -- I'm sending it here just to keep you all up to date on the
conversation.]

I'm not sure if I support this -- the 3.2.2 release is supposed to be purely
bug fixes.  Some of the work which has gone into mod_jk 3.3 are really new
features (support for WebDAV, for example).  

What do you see as the main reason for importing all changes into the 3.2
native code?

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.

I will take a look at the diffs and see if there any bug fixes which didn't
make it into 3.2.  I've tried to apply fixes to both branches.

-Dan

GOMEZ Henri wrote:
> 
> I didn't received replies to my post on mod_jk differences
> between TC 3.3 and TC 3.2.2.
> 
> I've proposed to copy all the mod_jk native code from TC 3.3 to
> TC 3.2.2 before release. They were many bugs fixed in both
> native and java parts, and it will be a pitty to let the release
> goes without that fixes.
> 
> I think that both Dan and Keith have each time back ported
> the Java corrections in tomcat_32 but it must be validated with them.
> 
> Another interest, is that mod_jk from TC 3.3 works with the latest
> Apache 2.0.
> 
> >-----Original Message-----
> >From: GOMEZ Henri [mailto:hgomez@slib.fr]
> >Sent: Friday, February 09, 2001 12:15 PM
> >To: tomcat-dev@jakarta.apache.org
> >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 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 reimported in TC 3.2.2 to avoid confusion and
> >mistake, and let us be sure we at the same level.
> >
> >What about ?
> >Who could do that ?
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, email: tomcat-dev-help@jakarta.apache.org

-- 

Dan Milstein // danmil@shore.net

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

[Keith Wannamaker <Ke...@Wannamaker.org>]

No, it was decided to not start changing the 3.2.x tree.
If people want the fixes, they can always upgrade.

Keith

-----Original Message-----

I think that both Dan and Keith have each time back ported 
the Java corrections in tomcat_32 but it must be validated with them.