On Tue, 16 Jul 2002, Ignacio J. Ortega <[EMAIL PROTECTED]> wrote: > I can remember that Sam said that this problem relates to use in the > build classpath some intermediate product of our build,
java.lang.InternalError: jzentry == 0 usually happens inside of Ant when you modify a jar that is on the CLASSPATH. on my box, Gump will run the build with <big snip /> export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-tomcat-connectors/coyote/build/lib/tomcat-coyote.jar export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-tomcat-4.0/build/server/lib/catalina.jar export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-tomcat-connectors/util/build/lib/tomcat-util.jar export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-servletapi-4/lib/servlet.jar export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-tomcat-4.0/catalina/build/server/classes <big snip /> and in the build log we see (Sam's box) > [jar] Building jar: > /home/rubys/jakarta/jakarta-tomcat-4.0/build/server/lib/catalina.jar so catalina.jar gets updated, this seems to be the thing that needs to be fixed (either don't build catalina.jar in tomcat-4.0 again or don't depend on tomcat-catalina). > revised logs, and nobody has changed anything in gump.xml or in > build.xml lately.., But then again it has been weeks since the last successful compile of Tomcat (mx4j is back for a few days only and since then Tomcat has been failing). Stefan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
