[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy:

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy: [ec

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy: [ec

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy: [ec

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy: [ec

[GUMP] Build Failure - jakarta-tomcat-4.0

This email is autogenerated from the output from: Buildfile: build.xml deploy-prepare: deploy-static: deploy: [ec

[GUMP] Build Failure - jakarta-tomcat-4.0

Buildfile: build.xml deploy-prepare: deploy-static: deploy: [echo] Target: Catalina - Deploy ... flags: flags.display: [ec

Re: [GUMP] Build Failure - jakarta-tomcat-4.0

We're working on that :-) It seems tomcat-util.jar was not available in the gump run, hopefully next gump will see it. Costin On 16 Apr 2002, Craig McClanahan wrote: > > This email is autogenerated from the output from: >

RE: [GUMP] Build Failure - jakarta-tomcat-4.0

[EMAIL PROTECTED]] > Sent: Tuesday, April 16, 2002 10:30 AM > To: Tomcat Developers List > Subject: Re: [GUMP] Build Failure - jakarta-tomcat-4.0 > > > > We're working on that :-) > > It seems tomcat-util.jar was not available in the gump run, > hopefull

RE: [GUMP] Build Failure - jakarta-tomcat-4.0

Larry Isaacs wrote: > > The build-main.classpath path ref looks okay to me as well. That mystery is pretty easy to clear up: http://jakarta.apache.org/gump/why.html#2000 http://jakarta.apache.org/ant/manual/sysclasspath.html http://jakarta.apache.org/gump/project.html#work - Sam Ruby

RE: [GUMP] Build Failure - jakarta-tomcat-4.0

By the way, gump runs are every six hours (see http://jakarta.apache.org/gump/ for details), so if you have a speculative fix that you would like to try out, make the change before a run, and check back later. Only the midnight PDT / 3.a.m. EDT runs cause nags. - Sam Ruby -- To unsubscribe, e-

RE: [GUMP] Build Failure - jakarta-tomcat-4.0

E: [GUMP] Build Failure - jakarta-tomcat-4.0 > > > By the way, gump runs are every six hours (see > http://jakarta.apache.org/gump/ for details), so if you have > a speculative > fix that you would like to try out, make the change before a > run, and check > back later.

RE: [GUMP] Build Failure - jakarta-tomcat-4.0

Larry Isaacs wrote: > > Thanks for the other tip. Are the nagoya runs still > being run? The result file is currently dated 4/4/02. Pier, do you know anything about the following? # Disabled GUMP to despool email... - Sam Ruby -- To unsubscribe, e-mail: For addi

Re: [GUMP] Build Failure - jakarta-tomcat-4.0

"Sam Ruby" <[EMAIL PROTECTED]> wrote: > Larry Isaacs wrote: >> >> Thanks for the other tip. Are the nagoya runs still >> being run? The result file is currently dated 4/4/02. > > Pier, do you know anything about the following? > > # Disabled GUMP to despool email... F***... I forgot to re-e

Re: [GUMP] Build Failure - jakarta-tomcat-4.0

> > jkjava: > [echo] Logging: >/home/rubys/jakarta/jakarta-commons/logging/dist/commons-logging.jar > [javac] Compiling 39 source files to >/home/rubys/jakarta/jakarta-tomcat-connectors/jk/build/classes > [javac] >/home/rubys/jakarta/jakarta-tomcat-connectors/jk/java/org/apache/jk

Re: [GUMP] Build Failure - jakarta-tomcat-4.0

Costin Manolache wrote: > > O k, that's crazy... All other step found tomcat.util - except this one. Note that this step is after the following line: > [jar] Building jar: >/home/rubys/jakarta/jakarta-tomcat-connectors/util/build/lib/tomcat-util.jar

RE: [GUMP] Build Failure - jakarta-tomcat-4.0

nal- > De: Craig McClanahan [mailto:[EMAIL PROTECTED]] > Enviado el: 16 de julio de 2002 16:38 > Para: [EMAIL PROTECTED] > Asunto: [GUMP] Build Failure - jakarta-tomcat-4.0 > > > > This email is autogenerated fr

Re: [GUMP] Build Failure - jakarta-tomcat-4.0

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

Re: [GUMP] Build Failure - jakarta-tomcat-4.0

I've removed the explicit dependency on tomcat-catalina from jakarta-tomcat-4.0 (i.e. you must remove line 78 from gump.xml) and it compiles a bit further (see below). This should remove the jzentry problem. The build itself fails while compiling Jasper, though: deploy: [echo] Target: Jasp