Re: Why is mod_jk distributed both as 2.0.2 and 2.0.4?
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 :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why is mod_jk distributed both as 2.0.2 and 2.0.4?
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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why is mod_jk distributed both as 2.0.2 and 2.0.4?
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]
Re: Why is mod_jk distributed both as 2.0.2 and 2.0.4?
From: Palle Girgensohn [EMAIL PROTECTED]
Hi!
How come this confusion about the latest version of mod_jk2? With the
jakarta-tomcat-connectors-4.1.2X, a mod_jk2 version 2.0.4 is distributed.
With
http://www.apache.org/dist/jakarta/tomcat-connectors/jk2/source/jakarta-tom
cat-connectors-jk2-src-current.tar.gz, the version is 2.0.2. Which one is
really current? Why this confusion?
As I understand it, the stable versions of the connector source are released
under the following directories:
mod_jk (currently 1.2.5):
jakarta/tomcat-connectors/jk/source/
mod_jk2 (currently 2.0.2):
jakarta/tomcat-connectors/jk2/source/
There are two parts to the connectors; the web server side (c) and the
tomcat side (java). I took a quick look at the current FreeBSD jk jk2
makefiles and they only make the apache portion. Assuming your ports are
tracking stable then they should be using the above source directories.
The FreeBSD jk2 port makefile has some problems. It is pointing to the jk
source dist file and building in the wrong wrksrc dir. Try these instead:
DISTNAME=jakarta-tomcat-connectors-jk2-${PORTVERSION}-src
WRKSRC=${WRKDIR}/jakarta-tomcat-connectors-jk2-${PORTVERSION}-src/jk/native2
For the java side, when tomcat is built it pulls from jtc HEAD. I'm not sure
why this is. Maybe someone else could elaborate on this?
-Kurt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why is mod_jk distributed both as 2.0.2 and 2.0.4?
On Tue, Nov 11, 2003 at 11:45:45AM -0500, Kurt Miller wrote: How come this confusion about the latest version of mod_jk2? With the jakarta-tomcat-connectors-4.1.2X, a mod_jk2 version 2.0.4 is distributed. With For the java side, when tomcat is built it pulls from jtc HEAD. I'm not sure why this is. Maybe someone else could elaborate on this? I noticed this too. I tried to build jk2 from jakarta-tomcat-connectors-4.1.29-src.tar.gz and it really didn't work. Several mappings from workers2.properties were broken. The version string in jk_globals.h is 2.0.3. Can we get a status update on the state of the world with regards to jk/jk2? Is CVS approaching stable? What is left to do? And, more importantly, what version currently released should we point users to? -- [EMAIL PROTECTED] Some people have a way with words, while others... erm... thingy. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why is mod_jk distributed both as 2.0.2 and 2.0.4?
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. -Kurt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Why is mod_jk distributed both as 2.0.2 and 2.0.4?
Hi! How come this confusion about the latest version of mod_jk2? With the jakarta-tomcat-connectors-4.1.2X, a mod_jk2 version 2.0.4 is distributed. With http://www.apache.org/dist/jakarta/tomcat-connectors/jk2/source/jakarta-tom cat-connectors-jk2-src-current.tar.gz, the version is 2.0.2. Which one is really current? Why this confusion? Regards, Palle Girgensohn FreeBSD mod_jk port maintainer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Why is mod_jk distributed both as 2.0.2 and 2.0.4?
-Original Message- From: Palle Girgensohn Hi! How come this confusion about the latest version of mod_jk2? With the jakarta-tomcat-connectors-4.1.2X, a mod_jk2 version 2.0.4 is distributed. With http://www.apache.org/dist/jakarta/tomcat-connectors/jk2/source/jakarta-tom cat-connectors-jk2-src-current.tar.gz, the version is 2.0.2. Which one is really current? Why this confusion? I've bumped the version to 2.0.4, (perhaps better would be 2.1.0). The jk2 that is in the cvs is highly experimental, cause we are using apr/apr-util as mandatory. Since 2.0.3 was never released (or will be), stay with 2.0.2 for a while. MT. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
