This email is autogenerated from the output from:
http://cvs.apache.org/builds/gump/2003-08-05/jakarta-tomcat.html
Buildfile: build.xml
detect:
uptodate:
msg.ant15:
[echo] Detected
This email is autogenerated from the output from:
http://cvs.apache.org/builds/gump/2003-08-07/jakarta-tomcat.html
Buildfile: build.xml
detect:
uptodate:
msg.ant15:
[echo] Detected
This email is autogenerated from the output from:
http://cvs.apache.org/builds/gump/2003-08-06/jakarta-tomcat.html
Buildfile: build.xml
detect:
uptodate:
msg.ant15:
[echo] Detected
This email is autogenerated from the output from:
http://cvs.apache.org/builds/gump/2003-01-25/jakarta-tomcat.html
Buildfile: build.xml
detect:
uptodate:
msg.ant15:
[echo] Detected
, January 25, 2003 1:05 AM
Subject: [GUMP] Build Failure - Tomcat 3.x
This email is autogenerated from the output from:
http://cvs.apache.org/builds/gump/2003-01-25/jakarta-tomcat.html
Bill,
Nacho: This has been working, like, forever (which with
Costin's Modeler
changes, is saying something :).If you did a straight
copy-over, then it
should still depend on commons-logging.
Hmmm, I dont completely understand you, i think, worked prior to the
move? it should work
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2002-07-30/jakarta-tomcat.html
Buildfile: build.xml
detect:
uptodate:
msg.jdk12:
[echo]
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2002-06-10/jakarta-tomcat.html
Buildfile: build.xml
detect:
uptodate:
msg.jdk12:
[echo]
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2002-06-08/jakarta-tomcat.html
Buildfile: build.xml
detect:
uptodate:
msg.jdk12:
[echo]
On 8 Jun 2002, Craig McClanahan wrote:
msg.jtc:
BUILD FAILED
/home/rubys/jakarta/jakarta-tomcat/build.xml:142: Jakarta-tomcat-connectors
repository is required /home/rubys/jakarta/jakarta-tomcat-connectors
It seems to be a regression with nightly ant - available returns false
even if the
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2002-04-14/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2002-04-13/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
Ignacio J. Ortega wrote:
We need to fix gump, not tomcat..
So... where is your patch?
I had one (other) person ask me for commit access... again without a patch.
I ultimately made the fix suggested... and this morning you see the result.
It is very difficult to build tomcat 3 and tomcat 4
On Sat, 13 Apr 2002, Sam Ruby wrote:
Ignacio J. Ortega wrote:
We need to fix gump, not tomcat..
So... where is your patch?
I had one (other) person ask me for commit access... again without a patch.
I ultimately made the fix suggested... and this morning you see the result.
It
Costin Manolache wrote:
Can we build j-t-c before tomcat(3,4) and add a special target for gump
that doesn't build j-t-c ?
I do build j-t-c (actually util subdirectory) before tomcat(3,4). Let me
know what target is desired.
BTW, wouldn't it be a good idea to keep the gump descriptors for
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2002-04-12/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
De: Pier Fumagalli [mailto:[EMAIL PROTECTED]]
Enviado el: viernes 12 de abril de 2002 15:10
Can someone fix the damn build? It's 3 days 3.x doesn't
build... A tree
which should be bugfix only...
Pier
We need to fix gump, not tomcat..
Saludos ,
Ignacio J. Ortega
--
To
Craig McClanahan [EMAIL PROTECTED] wrote:
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2002-04-12/jakarta-tomcat.html
Can someone fix the damn
Sam? Any clue on what's going on?
Pier
-- Forwarded Message
From: Ignacio J. Ortega [EMAIL PROTECTED]
Reply-To: Tomcat Developers List [EMAIL PROTECTED]
Date: Fri, 12 Apr 2002 15:25:58 +0200
To: 'Tomcat Developers List' [EMAIL PROTECTED]
Subject: RE: [GUMP] Build Failure - Tomcat 3.x
Ruby
Cc: Tomcat Developers List
Subject: FW: [GUMP] Build Failure - Tomcat 3.x
Sam? Any clue on what's going on?
Pier
-- Forwarded Message
From: Ignacio J. Ortega [EMAIL PROTECTED]
Reply-To: Tomcat Developers List [EMAIL PROTECTED]
Date: Fri, 12 Apr 2002 15:25:58 +0200
-Original Message-
From: Pier Fumagalli [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 12, 2002 9:30 AM
To: Sam Ruby
Cc: Tomcat Developers List
Subject: FW: [GUMP] Build Failure - Tomcat 3.x
Sam? Any clue on what's going on?
Pier
-- Forwarded Message
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2002-04-11/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2002-04-09/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2002-04-08/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-10-02/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-06-26/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-06-24/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-06-23/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-06-09/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-05-11/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
Please kick me out from this mailing list
- Original Message -
From: Craig McClanahan [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, May 09, 2001 2:32 PM
Subject: [GUMP] Build Failure - Tomcat 3.x
This email
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-05-10/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
On Wed, 9 May 2001 [EMAIL PROTECTED] wrote:
On 9 May 2001, Craig McClanahan wrote:
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-05-09/jakarta-tomcat.html
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-05-08/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-05-07/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
Ok, 2 changes in ant: copy no longer ignores inexisting source, and
the parser changed.
Both seem fair changes, we should fix the build.xml in tomcat.
I would like to use this oportunity to also upgrade to jaxp1.1.
( in order to avoid too much pain - since tomcat used to build with no
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-04-24/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
: Tuesday, April 24, 2001 8:45 AM
To: [EMAIL PROTECTED]
Subject: [GUMP] Build Failure - Tomcat 3.x
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-04-24/jakarta-tomcat.html
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-03-23/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-03-23/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-03-11/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
http://jakarta.apache.org/builds/gump/2001-03-11/jakarta-tomcat.html
This appears to be a classpath problem on my end. Will investigate.
- Sam Ruby
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email:
http://jakarta.apache.org/builds/gump/2001-03-11/jakarta-tomcat.html
This appears to be a classpath problem on my end. Will investigate.
Build changed - using jakarta-tomcat/build instead of ../build,
plus more.
The nightly is also broken, I'm working on it.
Costin
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-03-08/jakarta-tomcat.html
Buildfile: build.xml
init:
prepare:
[mkdir] Created dir:
Costin,
Is there any reasonable explanation for changing the ant structure ( i.e.
removing ant/bin ) ? Besides breaking backward compatibility and forcing
people to change their scripts ?
We like you to change your scripts on a regular basis to stop them getting
stale :-)
Seriously Ant's
Conor MacNeill wrote:
Costin,
Is there any reasonable explanation for changing the ant structure ( i.e.
removing ant/bin ) ? Besides breaking backward compatibility and forcing
people to change their scripts ?
We like you to change your scripts on a regular basis to stop them getting
Thanks Conor,
It was a double mistake - Sam set ant.home to a wrong value in gump and I
guessed wrong what was changed ( assuming the distribution layout
changed).
Tomcat doesn't depend on how ant build process works, only on the final
directory layout ( in the distrib ).
Meanwhile I updated
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-03-05/jakarta-tomcat.html
Buildfile: build.xml
init:
prepare:
[mkdir] Created dir:
Costin Manolache wrote:
Is there any reasonable explanation for changing the ant
structure ( i.e. removing ant/bin ) ? Besides breaking
backward compatibility and forcing people to change their
scripts
I can fix by specifying ant.home. What tomcat depends on is the
distribution layout,
I can fix by specifying ant.home. What tomcat depends on is the
distribution layout, i.e., "../jakarta-ant/dist".
Well, tomcat depends on having ant binaries ( in the normal format )
in ant.home.
The convention used is that "foo.home" is the place where a foo
distribution is installed, it
Costin Manolache wrote:
Well, tomcat depends on having ant binaries ( in the normal
format ) in ant.home.
Turns out I had made a change in the jakarta-ant definition (in order to
work around another problem), so the ant.home I was passing in the
jakarta-tomcat build was not valid.
My bug.
51 matches
Mail list logo