You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Sam Ruby <ru...@us.ibm.com> on 2001/03/05 22:27:58 UTC
[GUMP] Build Failure - Tomcat 3.x
----------------------------------------------------
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: /home/rubys/jakarta/build/tomcat
[mkdir] Created dir: /home/rubys/jakarta/build/tomcat/classes
[mkdir] Created dir: /home/rubys/jakarta/build/tomcat/conf
[mkdir] Created dir: /home/rubys/jakarta/build/tomcat/src
[mkdir] Created dir: /home/rubys/jakarta/build/tomcat/lib
[mkdir] Created dir: /home/rubys/jakarta/build/tomcat/lib/apps
[mkdir] Created dir: /home/rubys/jakarta/build/tomcat/lib/container
[mkdir] Created dir: /home/rubys/jakarta/build/tomcat/lib/common
[mkdir] Created dir: /home/rubys/jakarta/build/tomcat/logs
[mkdir] Created dir: /home/rubys/jakarta/build/tomcat/bin
[mkdir] Created dir: /home/rubys/jakarta/build/tomcat/doc
[mkdir] Created dir: /home/rubys/jakarta/build/tomcat/webapps
[mkdir] Created dir: /home/rubys/jakarta/build/tomcat/native
[copy] Copying 10 files to /home/rubys/jakarta/build/tomcat/bin
[copy] Copying 19 files to /home/rubys/jakarta/build/tomcat/conf
[copy] Copying 42 files to /home/rubys/jakarta/build/tomcat/doc
[copy] Copying 85 files to /home/rubys/jakarta/build/tomcat/native
[copy] Copying 1 file to /home/rubys/jakarta/build/tomcat
BUILD FAILED
/home/rubys/jakarta/jakarta-tomcat/build.xml:75: /home/rubys/jakarta/jakarta-ant/build/bin not found.
Total time: 11 seconds
Re: [GUMP] Build Failure - Tomcat 3.x
Posted by "Craig R. McClanahan" <Cr...@eng.sun.com>.
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
> stale :-)
>
Yah, we know :-)
I dealt with this particular change by setting my ANT_HOME environment variable
to "${my.jakarta.home}/jakarta-ant/dist" instead of
"${my.jakarta.home}/jakarta-ant". That way, everything that is resolved
relative to ANT_HOME works correctly, whether I'm using the current CVS source
code or a binary distro.
Craig
Re: [GUMP] Build Failure - Tomcat 3.x
Posted by cm...@yahoo.com.
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 ant, did a build - and congrats for the cleaned-up
build process ( I don't like building in the source dir, but I'll get
used to it :-).
Costin
On Tue, 6 Mar 2001, 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
> stale :-)
>
> Seriously Ant's build process was reorganized recently to build ant within
> the ant directory rather than above it. At that time, the bootstrapped Ant
> was moved into its own directory (bootstrap) so that generated jars
> (ant.jar) were not placed into a CVS directory (lib) where they may be
> inadvertently added to CVS. It made sense to move bin at the same time. If
> you have previously been using the ant/bin and ant/lib directories, you
> have actually been using the bootstrapped ant rather than the fully built
> ant. That is generally not a problem, of course, but perhaps not desirable.
> Also I think it is probably best for other projects not to rely on the
> internal organizaton of the Ant CVS tree but on the distribution built in
> the dist directory.
>
> Is that a "reasonable explanation" - you'll have to be the judge.
>
> Conor
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, email: tomcat-dev-help@jakarta.apache.org
>
Re: [GUMP] Build Failure - Tomcat 3.x
Posted by Conor MacNeill <co...@cognet.com.au>.
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 build process was reorganized recently to build ant within
the ant directory rather than above it. At that time, the bootstrapped Ant
was moved into its own directory (bootstrap) so that generated jars
(ant.jar) were not placed into a CVS directory (lib) where they may be
inadvertently added to CVS. It made sense to move bin at the same time. If
you have previously been using the ant/bin and ant/lib directories, you
have actually been using the bootstrapped ant rather than the fully built
ant. That is generally not a problem, of course, but perhaps not desirable.
Also I think it is probably best for other projects not to rely on the
internal organizaton of the Ant CVS tree but on the distribution built in
the dist directory.
Is that a "reasonable explanation" - you'll have to be the judge.
Conor
Re: [GUMP] Build Failure - Tomcat 3.x
Posted by cm...@yahoo.com.
> BUILD FAILED
>
> /home/rubys/jakarta/jakarta-tomcat/build.xml:75: /home/rubys/jakarta/jakarta-ant/build/bin not found.
Well, I can fix this - but as the comment says, ant is needed for testing
and various other tasks.
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 ?
Costin