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 Nabble.com.
---
A lot of our build.xmls contain things like this, where “ls -l /tmp” is just
some arbitrary command:
ls -l /tmp
When you run this (with verbosity on), you get the output of ls. So far so
good.
What you *don’t* get is what command just ran. In this case, we do not see
“ls -l /t
