RE: [ANNOUNCE] Tomcat 4.0 Release Candidate 1 Available
-Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] I *finally* got to these suggested patches, and have commited changes to catalina.sh, digest.sh, and jasper.sh to implement Cygwin support consistently and (hopefully) correctly. Could you please try all of these scripts with tonight's nightly build (20010912) to make sure that I didn't mess anything up? catalina.sh works like a charm. jasper.sh I have a small glitch in the classpath when running jasper but I don't know where it is coming from. I have an invalid character sets in the middle of the classpath when converting the paths back to windows. Seems to be a cygwin issue with loong paths, since i have no problems with short paths. If someone with cygwin could check this it would be nice. see in the middle of the classpath: I have a jakart ?mcat-4.0 bash-2.05$ jasper.sh Guessing JASPER_HOME from catalina.sh to ./.. Setting JASPER_HOME to ./.. Using CLASSPATH: .;m:\sb_desproto\desproto\ichannel\lib\tomcat\jakarta-tomcat-4.0\classes;m:\ sb_desproto\desproto\ichannel\lib\tomcat\jakarta-tomcat-4.0\lib\jasper-runti me.jar;m:\sb_desproto\desproto\ichannel\lib\tomcat\jakarta-tomcat-4.0\common \lib\servlet.jar;m:\sb_desproto\desproto\ichannel\lib\tomcat\jakarta-tomcat- 4.0\lib\namingfactory.jar;m:\sb_desproto\desproto\ichannel\lib\tomcat\jakart a-tomcat-4.0\common\lib\servlet.jar;m:\sb_desproto\desproto\ichannel\lib\tom cat\jakarta-tomcat-4.0\jasper\crimson.jar;m:\sb_desproto\desproto\ichannel\l ib\tomcat\jakart ?mcat-4.0\common\lib\servlet.jar;m:\sb_desproto\desproto\ichannel\lib\tomcat \jakarta-tomcat-4.0\jasper\jasper-compiler.jar;m:\sb_desproto\desproto\ichan nel\lib\tomcat\jakarta-tomcat-4.0\common\lib\servlet.jar;m:\sb_desproto\desp roto\ichannel\lib\tomcat\jakarta-tomcat-4.0\jasper\jaxp.jar;m:\sb_desproto\d esproto\ichannel\lib\tomcat\jakarta-tomcat-4.0\common\lib\servlet.jar Using JASPER_HOME: m:\sb_desproto\desproto\ichannel\lib\tomcat\jakarta-tomcat-4.0 Using JAVA_HOME: e:\jdk\jdk1.3.1 Usage: jasper.sh ( jspc ) Commands: jspc - Run the jasper offline JSP compiler However, jasper.bat is incorrect. It sets JASPER_HOME=. and looks for %JASPER_HOME%\bin\jappend.bat Should be JASPER_HOME=.. Stephane
RE: [ANNOUNCE] Tomcat 4.0 Release Candidate 1 Available
I should have jasper.sh working correctly now. It was using CP the first time without initializing it, and was missing some double quotes that could cause problems with paths that had spaces in them. Will be fixed in nightly build 20010914 (and rc2). Craig On Thu, 13 Sep 2001, Stephane Bailliez wrote: Date: Thu, 13 Sep 2001 10:15:49 +0100 From: Stephane Bailliez [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: [ANNOUNCE] Tomcat 4.0 Release Candidate 1 Available -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] I *finally* got to these suggested patches, and have commited changes to catalina.sh, digest.sh, and jasper.sh to implement Cygwin support consistently and (hopefully) correctly. Could you please try all of these scripts with tonight's nightly build (20010912) to make sure that I didn't mess anything up? catalina.sh works like a charm. jasper.sh I have a small glitch in the classpath when running jasper but I don't know where it is coming from. I have an invalid character sets in the middle of the classpath when converting the paths back to windows. Seems to be a cygwin issue with loong paths, since i have no problems with short paths. If someone with cygwin could check this it would be nice. see in the middle of the classpath: I have a jakart ?mcat-4.0 bash-2.05$ jasper.sh Guessing JASPER_HOME from catalina.sh to ./.. Setting JASPER_HOME to ./.. Using CLASSPATH: .;m:\sb_desproto\desproto\ichannel\lib\tomcat\jakarta-tomcat-4.0\classes;m:\ sb_desproto\desproto\ichannel\lib\tomcat\jakarta-tomcat-4.0\lib\jasper-runti me.jar;m:\sb_desproto\desproto\ichannel\lib\tomcat\jakarta-tomcat-4.0\common \lib\servlet.jar;m:\sb_desproto\desproto\ichannel\lib\tomcat\jakarta-tomcat- 4.0\lib\namingfactory.jar;m:\sb_desproto\desproto\ichannel\lib\tomcat\jakart a-tomcat-4.0\common\lib\servlet.jar;m:\sb_desproto\desproto\ichannel\lib\tom cat\jakarta-tomcat-4.0\jasper\crimson.jar;m:\sb_desproto\desproto\ichannel\l ib\tomcat\jakart ?mcat-4.0\common\lib\servlet.jar;m:\sb_desproto\desproto\ichannel\lib\tomcat \jakarta-tomcat-4.0\jasper\jasper-compiler.jar;m:\sb_desproto\desproto\ichan nel\lib\tomcat\jakarta-tomcat-4.0\common\lib\servlet.jar;m:\sb_desproto\desp roto\ichannel\lib\tomcat\jakarta-tomcat-4.0\jasper\jaxp.jar;m:\sb_desproto\d esproto\ichannel\lib\tomcat\jakarta-tomcat-4.0\common\lib\servlet.jar Using JASPER_HOME: m:\sb_desproto\desproto\ichannel\lib\tomcat\jakarta-tomcat-4.0 Using JAVA_HOME: e:\jdk\jdk1.3.1 Usage: jasper.sh ( jspc ) Commands: jspc - Run the jasper offline JSP compiler However, jasper.bat is incorrect. It sets JASPER_HOME=. and looks for %JASPER_HOME%\bin\jappend.bat Should be JASPER_HOME=.. Stephane
RE: [ANNOUNCE] Tomcat 4.0 Release Candidate 1 Available
On Mon, 10 Sep 2001, Stephane Bailliez wrote: Date: Mon, 10 Sep 2001 09:19:32 +0100 From: Stephane Bailliez [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: [ANNOUNCE] Tomcat 4.0 Release Candidate 1 Available Craig, I'm desperately trying for weeks to have a patch committed concerning catalina.sh that does not work under cygwin. Bip committed the one on digest.sh but catalina.sh and jasper.sh are still pending. http://marc.theaimsgroup.com/?l=tomcat-devm=99830164420886w=2 I would be grateful if this could be fixed before the release... The current cygwin magic simply does not work because the process must be: 1) convert everything into unix like paths 2) manipulate paths 3) convert back to the windows like paths. 4) run the java process The step 1 is missing thus it will fail on windows because paths will be a mixed of unix/windows separators. Stephane, I *finally* got to these suggested patches, and have commited changes to catalina.sh, digest.sh, and jasper.sh to implement Cygwin support consistently and (hopefully) correctly. Could you please try all of these scripts with tonight's nightly build (20010912) to make sure that I didn't mess anything up? Cheers, -- Stephane Bailliez Thanks, Craig
RE: [ANNOUNCE] Tomcat 4.0 Release Candidate 1 Available
On Mon, 10 Sep 2001, David Oxley wrote: Date: Mon, 10 Sep 2001 10:52:14 +0100 From: David Oxley [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] Subject: RE: [ANNOUNCE] Tomcat 4.0 Release Candidate 1 Available Craig, What will the state of TC4 be at release. I believe mod_webapp is not yet finished and the service code is also nowhere near complete. Are these features going to be delivered in TC4.0.1 or TC4.1, because until they're available I cannot (and probably many others) use TC4 in production. I don't mean to sound complaining, I think you guys have created the basis for a superb product with TC4. The final choice will be up to the TOMCAT-DEV committers when presented with the final release candidate to be voted on. I can appreciate your concerns about the webapp connector and the service code. However, there are undoubtedly also many users who do *not* need these two features, but need a stable implementation of the new specs. Is it fair to delay the entire release for these two featuers -- especially when other alternatives are available (i.e. you can use mod_jk with Tomcat 4, and there are many NT Service gadgets for Java applications)? It will be an interesting discussion to see how this plays out. Thanks. Dave. [EMAIL PROTECTED] Craig -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: 10 September 2001 07:31 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [ANNOUNCE] Tomcat 4.0 Release Candidate 1 Available The first Release Candidate for Tomcat 4.0 is now available. Only serious problems will be fixed between now and final release of Tomcat 4.0, which is currently scheduled for September 17, 2001. A second release candidate, if necessary, will be distributed on Thursday, September 13. Please download this version and run your existing web applications against it, to help us ensure a final release that is as trouble free as possible. The release is available at: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-rc1/ and bug reports should be submitted to: http://nagoya.apache.org/bugzilla/ under product category Tomcat 4. Craig McClanahan
