I've noticed an interesting problem with the shell script that starts ant for the UNIX flavours.
If someone sets JAVACMD to an executable WITH parameters, then one line in
the script fails, the line that goes something like this:
if [ ! -x $JAVACMD ] ; then ....
To prove this, I wrote a test script. It goes like this:
#!/bin/sh
cmd="a";
if [ -x "$cmd" ] ; then
echo "first command found"
else
echo "first command not found"
fi
cmd="a a";
if [ -x "$cmd" ] ; then
echo "second command found"
else
echo "second command not found"
fi
I have a second script in the same directory, called "a". The output of my
test gave me the following:
07:20:55 $ b
first command found
second command not found
[EMAIL PROTECTED]://f/temp
07:20:59 $
As you can see, the -x test only works if it's tester does not have any
arguments. Why is this a problem? Well, my JAVACMD looks like this:
JAVACMD='java -Xmx256m'
which is perfectly legal (I believe).
Therefore, this patch simply removes code introduced in ant (the shell
script) version 1.5.
<<ant.diff>>
--
Jay Dickon Glanville
P068 - SiteManager Development, Nortel Networks
613-765-1144 (ESN 395-1144)
MS: 045/55/A05
E-Mail: [EMAIL PROTECTED]
ant.diff
Description: Binary data
