Re: Why is mod_jk distributed both as 2.0.2 and 2.0.4?

[Glenn Nielsen]

Kurt Miller wrote:
From: "Henri Gomez" <[EMAIL PROTECTED]>

Kurt Miller a écrit :


From: "Glenn Nielsen" <[EMAIL PROTECTED]>

Perhaps the mod_jk connector should not be released with Tomcat 4/5

since

it


has its own release cycle and we are already doing separate releases of
these.
Regards,

Glenn



Would this work...

When a stable version of mod_jk or mod_jk2 is released put the stable

jar

files in the
jakarta/tomcat-connectors/jk(2)/binaries/ directories. Then have Tomcat

4/5

use the released stable jars instead of building them.

If this works, then it may also serve as a way for users to upgrade both

the

native and the java side when a new jk/jk2 release is made.
I think that we should decouple jk/jk2 release from tomcat3/4/5 release,
in some case jk 1.2.x add a faster release rate that tomcats :)


I guess the simplest solution is to exclude the following directories from
the jakarta-tomcat-connectors-4.X-src archives to avoid confusion:
jk/native
jk/native2
webapp/apache-1.3
webapp/apache-2.0
webapp/lib
webapp/support
webapp/include
Another way to look at this is, what things out of j-t-c need to have
a source release along with a Tomct 3/4/5 release?  Remy?
coyote, http11, and util, anything else?

Would we then need to provide jars and source for the AJP connector side
of things in our mod_jk releases?
Regards,

Glenn

----------------------------------------------------------------------
Glenn Nielsen             [EMAIL PROTECTED] | /* Spelin donut madder    |
MOREnet System Programming               |  * if iz ina coment.      |
Missouri Research and Education Network  |  */                       |
----------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]