Kevin O'Neill wrote:
Just installed YUM, quite neat, thanks. Being a dinosaur and having worked on some 20 flavours of *nix over the years I have always shied away from proprietary install facilities such as RPM and installed by hand from the tar or zip. After spending the last 5 years stable on Red Has Linux, maybe I should get over that. Hmm...I have had thoughts of moving over to OSX, but that is another story ;-)Okay. Well here is my config. I'm running RedHat 9, ant from JPackage (Installed via YUM, love YUM). I don't use build.sh I just run ant.
I agree with this. It is quite possible to build an ant script that is platform independent and that sorts out all the dependencies. Having another layer just creates yet another thing that needs to be looked at when the configuration changes. Poor return on investment. Btw, I general I am for including all need dependencies in the project's cvs repository, unless of course you are using Maven. I do not think, however, that this should apply to ant and junit. These are tools not build dependencies. I certain versions of the are needed that can be checked in the build script.Check that /etc/ant.conf isn't overriding ANT_HOME (in my case it does, making build.sh ineffective). Personally I'd like to see an end to the build.sh's of the world :).
I'm running 1.4.2 (I'm not sure that would have a difference though).
The problem is clearly in the build.sh file. Once I got the junit jars into my ant lib directory everything works fine,
IFF the consensus of opinion is that the build.sh and build.bat files are to be maintained, then I will be happy to look at the shell script to figure out why it is not working. Personally, though, I vote -1 on keeping them and +1 to improve the ant script is it is even necessary,
- joel
