D]
Sent: Friday, November 05, 2004 11:14 AM
To: Ant Users List
Subject: RE: passing Ant property values to new build
> From: Casey Daniell [mailto:[EMAIL PROTECTED]
>
> for some reason if I pass in a value that is the same as the
> property name I am trying to use it doesn't evaluate t
> From: Casey Daniell [mailto:[EMAIL PROTECTED]
>
> for some reason if I pass in a value that is the same as the
> property name I am trying to use it doesn't evaluate the var
> properly. A bug perhaps? I am using ANT 1.6.2
Hmmm... Would you mind creating a small Ant snippet that demonstrates
tha
AM
To: [EMAIL PROTECTED]
Subject: AW: passing Ant property values to new build
Is the property set? Do a
$${tools.home}=${tools.home}
directly before the .
Jan
> -Ursprüngliche Nachricht-
> Von: Casey Daniell [mailto:[EMAIL PROTECTED]
> Gesendet am: Freitag, 5. November 2
> From: Casey Daniell [mailto:[EMAIL PROTECTED]
> Here is the problem. I am have one ant script calling another via the
ant
> task. I want the value of a property to be transmitted to the new
build
> not
> the string literal itself.
>
> Ex.
>basedir == /foo (not in any syntax)
>
>
>
>
Is the property set? Do a
$${tools.home}=${tools.home}
directly before the .
Jan
> -Ursprüngliche Nachricht-
> Von: Casey Daniell [mailto:[EMAIL PROTECTED]
> Gesendet am: Freitag, 5. November 2004 17:45
> An: '[EMAIL PROTECTED]'
> Betreff: passing Ant pro
All,
I am a long time ant user but for some reason I am stumped on this, maybe
its too early in the morning.
Here is the problem. I am have one ant script calling another via the ant
task. I want the value of a property to be transmitted to the new build not
the string literal itself.
Ex.
