I recently upgraded to tomcat 4.1.24 from 4.1.18. After performing this upgrade, whenever I try to deploy a new version of a JSP page on the server, the compile fails. I have tracked this down to this bit of the stack trace:
Caused by: java.io.IOException: CreateProcess: javac.exe -classpath D:\Tomcat418\bin\bootstrap.jar;D:\Tomcat418\webapps\wwxchange\WEB-INF\lib\Li nearBarCode.jar;D:\Tomcat418\webapps\wwxchange\WEB-INF\lib\WWXchange.jar;D:\ Tomcat418\shared\classes;D:\Tomcat418\common\classes;D:\Tomcat418\common\lib \activation.jar;D:\Tomcat418\common\lib\ant.jar;D:\Tomcat418\common\lib\comm ons-collections.jar;D:\Tomcat418\common\lib\commons-dbcp.jar;D:\Tomcat418\co mmon\lib\commons-httpclient-2.0-beta1.jar;D:\Tomcat418\common\lib\commons-lo gging-api.jar;D:\Tomcat418\common\lib\commons-logging.jar;D:\Tomcat418\commo n\lib\commons-pool.jar;D:\Tomcat418\common\lib\Commons.jar;D:\Tomcat418\comm on\lib\EJOB.jar;D:\Tomcat418\common\lib\ftpbean.jar;D:\Tomcat418\common\lib\ jakarta-poi-1.10.0-dev-20030222.jar;D:\Tomcat418\common\lib\jasper-compiler. jar;D:\Tomcat418\common\lib\jasper-runtime.jar;D:\Tomcat418\common\lib\mail. jar;D:\Tomcat418\common\lib\mm.mysql-2.0.14-bin.jar;D:\Tomcat418\common\lib\ naming-common.jar;D:\Tomcat418\common\lib\naming-factory.jar;D:\Tomcat418\co ? It seems like ant is truncating the classpath. Does this need to be posted to the ant mailing list? If not, the only workaround I can find is to unpack jars to the common/classes directory, thus shortening the classpath. Does anybody know a "cleaner" way to handle this? --Nathan McMinn
