Stefan Bodewig wrote:
On Mon, 23 May 2005, Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote:
we should add a line about in in the table explainning the different
system properties used by Ant.
Keep in mind that it is our wrapper script that sets the property. If
you launch ant any other way (IDE, script of your own, embedded),
there is no guarantee that it will be defined.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
But that's precisely my use case. In an environment where there is more
than one way to launch ant, I sometimes get unexpected results. In my
case I've got a JPackage install, plus various trees of various versions
of ant in various stages of development. When something hasn't worked
they way I want, I need to go see what ANT_HOME was defined as at the
moment Ant launched. I don't want to do anything with it, I just want
to see how it was defined, without reading a lot of shell scripts trying
to understand which path got me where I am. In fact, knowing what
ANT_HOME was eventually chosen makes it easier to follow the shell
scripts. If ANT_HOME is not defined, that also is worth knowing.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
