I have found a pretty good solution... Since has been posted a couple of
times over the last few years here is what I found.
When you run "ANT" from a windows box it actually runs ANT.bat from the
%ANT_HOME%\bin\ folder. This is the wrapper script and they already "slurp"
up the command line into a variable called "ANT_CMD_LINE_ARGS"
So from there a quick import of the environment vars with
<property environment ="env"/>
at the top of the build file and this line inserted some time after the
record statement
<echo>ANT ${env.ANT_CMD_LINE_ARGS}</echo>
and I have now recorded the command line that was used to create the build
in the first place.
I did notice that the runAnt.bat and other forms or runAnt did not use the
same variable so this might not work as well if you are using the runANT
flavor of launch scripts.
--
View this message in context:
http://old.nabble.com/What-was-the-ANT-Command-Line--tp26416508p26421369.html
Sent from the Ant - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@ant.apache.org
For additional commands, e-mail: user-h...@ant.apache.org
