You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Stefan Bodewig <bo...@bost.de> on 2000/07/14 12:25:11 UTC
What is the purpose of build.sh?
In the light of Conor's changes and looking at Sam's script in
<URL:http://oss.software.ibm.com/developerworks/opensource/jakarta/buildall.html>
(all his builds fail since the changes) I'm a little bit puzzled.
What is build.sh supposed to do?
The way Sam uses it looks as if build.sh was a wrapper around ant to
build arbitrary projects - I thought that bin/ant is the right thing
to use.
The way Conor has changed it, it becomes unusable unless your current
working directory is ${ANT_HOME} - otherwise it is going to run
./bootstrap.sh and fails in turn because this will probably not exist
(as opposed to ${ANT_HOME}/bootstrap.sh).
It wouldn't be too difficult to revert the behavior back to what the
old build.sh did - I just don't see why we'd need it and not use
bin/ant directly.
Could somebody please help me out?
Stefan
Re: What is the purpose of build.sh?
Posted by Stefan Bodewig <bo...@bost.de>.
>>>>> "CM" == Conor MacNeill <co...@m64.com> writes:
CM> I think Sam would know that since he summarised the situation
CM> prior to my actually making the changes.
I had seen that thread but not really followed it.
CM> I think it is a semi standard that jakarta projects include a
CM> build.sh/build.bat to allow you to build the project right out of
CM> CVS. The automatic bootstrap makes this simpler for the
CM> first-time ant builder.
OK, I see. For my bootstrap.sh and ant seemed to be enough so I was
really puzzled what the build.sh was intended to do. If it is for the
convinience of users that know other jakarta project, I'm fine with
it.
Thanks for the clarification.
Stefan
RE: What is the purpose of build.sh?
Posted by Conor MacNeill <co...@m64.com>.
Stefan,
I have let Sam know that I broke his builds :-(. It was to be expected and I
think Sam would know that since he summarised the situation prior to my
actually making the changes.
build.sh is now JUST for building ant. It cannot be used to build other ant
based projects. The script does assume that you are running it in the same
directory. It is, however, still useful to have build.sh/build.bat for a
number of reasons.
I think it is a semi standard that jakarta projects include a
build.sh/build.bat to allow you to build the project right out of CVS. The
automatic bootstrap makes this simpler for the first-time ant builder.
The ability to install ant into $ANT_HOME is also useful. Normally it is
somewhat dangerous to overwrite the scripts and jars from which you are
running. build fullinstall allows you to install into the ANT_HOME without
having to run the ant that lives there.
At Sam's suggestion I made build.sh/build.bat simple drivers for
ant/ant.bat. This reduces the duplication of code that had been the case
prior to these changes.
I am hoping Sam changes his build scripts to use ant rather than build.sh
i.e. change /home/rubys/jakarta-ant/build.sh to
/home/rubys/jakarta-ant/bin/ant
presuming ANT_HOME is set appropriately or unset altogether.
What do you think?
Conor
> -----Original Message-----
> From: Stefan Bodewig [mailto:bodewig@bost.de]
> Sent: Friday, July 14, 2000 8:25 PM
> To: ant-dev@jakarta.apache.org
> Subject: What is the purpose of build.sh?
>
>
> In the light of Conor's changes and looking at Sam's script in
> <URL:http://oss.software.ibm.com/developerworks/opensource/jakarta
> /buildall.html>
> (all his builds fail since the changes) I'm a little bit puzzled.
>
> What is build.sh supposed to do?
>
> The way Sam uses it looks as if build.sh was a wrapper around ant to
> build arbitrary projects - I thought that bin/ant is the right thing
> to use.
>
> The way Conor has changed it, it becomes unusable unless your current
> working directory is ${ANT_HOME} - otherwise it is going to run
> ./bootstrap.sh and fails in turn because this will probably not exist
> (as opposed to ${ANT_HOME}/bootstrap.sh).
>
> It wouldn't be too difficult to revert the behavior back to what the
> old build.sh did - I just don't see why we'd need it and not use
> bin/ant directly.
>
> Could somebody please help me out?
>
> Stefan
>