Re: JK versions status and web pages ?
GOMEZ Henri wrote: What's the final status of versioning ? - jtc/jk/native mod_jk 1.2 - jtc/jk/native2mod_jk 2.0 So we could make soon a release of mod_jk 1.2. BTW: I need guidelines to create the JTC, at least jk webpages. - Did we have to choose anakia / buildsite ? Anakia so that it looks like the rest of jakarta.apache.org. - what will be the URL ? (http://jakarta.apache.org/jtc/) ? http://jakarta.apache.org/tomcat/connectors/? where will it be put on jakarta.apache.org ? Add a link in http://jakarta.apache.org/tomcat/index.html I plan to move some of the current Tomcat 3.3 documents, ie mod_jk, IIS, part of SSL to this page. I would also put there the mod_webapp existing documents. - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 04, 2001 10:12 AM To: Tomcat Developers List Subject: RE: JK versions After reading the commit log - most changes related to jk_channel, jk_registry, etc are pretty safe ( as they don't change any logic ). We could actually release Jk1.2 using the main tree - if everyone is comfortable with that. If not - Oct21 is probably a good point to branch ( the release date for 3.3 ). There are few fixes for ebcdic support and few small things that would have to be re-applied. Let's get the old version, and then I'll reapply the EBCDIC changes. We should keep ajp12 is JK 1.2 :) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JK versions
After reading the commit log - most changes related to jk_channel, jk_registry, etc are pretty safe ( as they don't change any logic ). We could actually release Jk1.2 using the main tree - if everyone is comfortable with that. If not - Oct21 is probably a good point to branch ( the release date for 3.3 ). There are few fixes for ebcdic support and few small things that would have to be re-applied. Let's get the old version, and then I'll reapply the EBCDIC changes. We should keep ajp12 is JK 1.2 :) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JK versions
I will not check anything else into mod_jk until this is decided ( since my next commit is pretty big and likely to brake things, I did a lot of changes in uri_map, etc. - I need a stable branch labeled before doing the commit ). Ok, let's release mod_jk to 1.2 and start 2.0. The refactoring is massive but until it will be finished we'll need a running and working mod_jk. What we should do : - Release it (1.2) - make binaries for all knowns platform (Apache w/o SSL, IIS, iPlanet, Domino) - Create a link to this repository which could be used by both Tomcat 3.2, 3.3, 4.0 - And may be start to think about creating web pages for J-T-C -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JK versions
| - And may be start to think about creating web pages | for J-T-C A small webpage with something like download mod_jk on it would do the trick for now! Anything is better than nothing! And a link to it from the Tomcat webpages would really be something! It's IMPOSSIBLE to find things now. Really really bad.. yes, I agree ! i'll have to play with anakia and jakarta-site if nobody else is candidate ;( -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: JK versions
I will not check anything else into mod_jk until this is decided ( since my next commit is pretty big and likely to brake things, I did a lot of changes in uri_map, etc. - I need a stable branch labeled before doing the commit ). Ok, let's release mod_jk to 1.2 and start 2.0. The refactoring is massive but until it will be finished we'll need a running and working mod_jk. What we should do : - Release it (1.2) - make binaries for all knowns platform (Apache w/o SSL, IIS, iPlanet, Domino) - Create a link to this repository which could be used by both Tomcat 3.2, 3.3, 4.0 - And may be start to think about creating web pages for J-T-C +1. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: JK versions
+1 GOMEZ Henri wrote: I will not check anything else into mod_jk until this is decided ( since my next commit is pretty big and likely to brake things, I did a lot of changes in uri_map, etc. - I need a stable branch labeled before doing the commit ). Ok, let's release mod_jk to 1.2 and start 2.0. The refactoring is massive but until it will be finished we'll need a running and working mod_jk. What we should do : - Release it (1.2) - make binaries for all knowns platform (Apache w/o SSL, IIS, iPlanet, Domino) - Create a link to this repository which could be used by both Tomcat 3.2, 3.3, 4.0 - And may be start to think about creating web pages for J-T-C -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Andy Armstrong, Tagish -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JK versions
On Mon, 3 Dec 2001, GOMEZ Henri wrote: Ok, let's release mod_jk to 1.2 and start 2.0. What I did is put all the new stuff in native2. There are few other (big) changes coming, I hope to get it back into a 'stable' state by the end of the week and start updating the iis,nes,etc ( now I'm working on a single server adapter, it's much easier ). For 1.2 we have 2 choices: - Branch it at Nov 15 ( or around ), i.e. before jk_channel and the new stuff ( that will be part of jk2.0 ) was added. - revert the changes ( it should be easy - just copy the files as of Nov15 over and commit ), and stay in the main branch ( with a tag, etc). I prefer the second choice, since we could build both jk1.2 and jk2 out of the same space and it's easier to work ( that's how xalan managed the repository for example ). If we tag only a subdir, a checkout with the tag will get only the tagged files anyway. The only issue is if any bug fix was done between Nov15 and today in the main branch. If so, it'll be included in 2.0 but not in 1.2. I'll take a look at the commit messages and see if I can find any, and apply it again. - Release it (1.2) - make binaries for all knowns platform (Apache w/o SSL, IIS, iPlanet, Domino) - Create a link to this repository which could be used by both Tomcat 3.2, 3.3, 4.0 - And may be start to think about creating web pages for J-T-C It seems we have agreement, all we need now is volunteers :-) Could you... :-) ?? Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JK versions
On Mon, 3 Dec 2001 [EMAIL PROTECTED] wrote: On Mon, 3 Dec 2001, GOMEZ Henri wrote: Ok, let's release mod_jk to 1.2 and start 2.0. For 1.2 we have 2 choices: - Branch it at Nov 15 ( or around ), i.e. before jk_channel and the new stuff ( that will be part of jk2.0 ) was added. After reading the commit log - most changes related to jk_channel, jk_registry, etc are pretty safe ( as they don't change any logic ). We could actually release Jk1.2 using the main tree - if everyone is comfortable with that. If not - Oct21 is probably a good point to branch ( the release date for 3.3 ). There are few fixes for ebcdic support and few small things that would have to be re-applied. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JK versions
[EMAIL PROTECTED] 12/03/01 01:53PM On Mon, 3 Dec 2001 [EMAIL PROTECTED] wrote: On Mon, 3 Dec 2001, GOMEZ Henri wrote: Ok, let's release mod_jk to 1.2 and start 2.0. For 1.2 we have 2 choices: - Branch it at Nov 15 ( or around ), i.e. before jk_channel and the new stuff ( that will be part of jk2.0 ) was added. After reading the commit log - most changes related to jk_channel, jk_registry, etc are pretty safe ( as they don't change any logic ). We could actually release Jk1.2 using the main tree - if everyone is comfortable with that. If not - Oct21 is probably a good point to branch ( the release date for 3.3 ). I'm afraid that we need to go back to an earlier date and re-port some fixes. The main reason is because the default 3.3 workers.properties still reference ajp12 which the current codebase no longer supports. This causes the plugins to fail during initialization since the ajp12_worker_factory isn't even in the main tree. Either that, or we add ajp12 support back in long enough to do a release. I'll be happy to help either way. There are few fixes for ebcdic support and few small things that would have to be re-applied. Costin Mike Anderson -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JK versions
On Mon, 3 Dec 2001, Mike Anderson wrote: I'm afraid that we need to go back to an earlier date and re-port some fixes. The main reason is because the default 3.3 workers.properties still reference ajp12 which the current codebase no longer supports. This causes the plugins to fail during initialization since the ajp12_worker_factory isn't even in the main tree. Either that, or we add ajp12 support back in long enough to do a release. I'll be happy to help either way. I think ajp12 must be included in JK1.2 one way or the other. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: JK versions
[EMAIL PROTECTED] wrote: What I would like to do is make a branch for mod_jk 1.2, and eventually build a snapshot. If I'm getting this right, you are trying to preserve 1.2 for bug fixing a backward compatibility, while focusing on 2.0. Yes? If so, I'm [+1] for it as it seems very reasonable. Bojan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: JK versions
There is an important issue to discuss - labeling mod_jk. As you know, we are trying to make some improvements in jk, start using APR, etc. That will involve few significant changes - and some people may want to have a more 'stable' jk. There are 4 versions of jk: Let's call 1.0 what is present in tomcat3.2.x repository. Let's call 1.1 what is present in 3.3 repository. It is backward compatible with Jk1.0, has many fixes, etc. 1.2 - what is in jakarta-tomcat-connectors/jk, the same as 1.1 plus support for Apache2.0 ( Jk1.1 doesn't support apache2.0 since it wasn't available at that time ). This version also have support for tomcat4.0 and initial code for ajp14. I would call '1.2' the version that was in CVS around Oct 15 ( i.e. after both 3.3 and 4.0.1 were released, before any refactoring was started ). So far all the changes in the main tree were small. However some biger changes are needed and are already in progress. We'll have a simpler build system, support for APR, lot more flexibility, simpler configuration. I would like to call the next version of jk 2.0, as a number of internal APIs will change. ( all those numbers are made up - we can call them 1, 2, 3, 4 instead of 1.0, 1.1, ... ). What I would like to do is make a branch for mod_jk 1.2, and eventually build a snapshot. Eventually we should start a release plan and have a vote on the names and such. Since names/labels/versions are allways fun thing to discuss, I'm open to any other naming scheme - but we need to have one, it's extremely confusing otherwise. I will not check anything else into mod_jk until this is decided ( since my next commit is pretty big and likely to brake things, I did a lot of changes in uri_map, etc. - I need a stable branch labeled before doing the commit ). +1. Tag it (or branch it) ! Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
