that's a good idea. I'll create a macrodef to do just that.
--
View this message in context:
http://ant.1045680.n5.nabble.com/determine-what-shellscript-just-ran-tp5143649p5148852.html
Sent from the Ant - Users mailing list archive at
Why not create a macrodef that echoes the input command and then calls the
ant-contrib task?
From my HTC Sensation 4G on T-Mobile. The first nationwide 4G network
- Reply message -
From: "Peter Reilly"
To: "Ant Users List"
Subject: determine what shellscript just r
the output of ant), and I can't
> tell what command caused what output.
>
>
> --
> View this message in context:
> http://ant.1045680.n5.nabble.com/determine-what-shellscript-just-ran-tp5143649p5143649.html
> Sent from the Ant - Users mailing list archive at Nabble.com.
t ran?
I have a bunch of build logs (which is just the output of ant), and I can't
tell what command caused what output.
--
View this message in context:
http://ant.1045680.n5.nabble.com/determine-what-shellscript-just-ran-tp5143649p5143649.html
Sent from the Ant - Users mail
