Man, there sure is a lot of confusion about how to use properties properly
in Ant.... somebody oughta write a book about this stuff...
Replace everything you have below with this:
<property environment="env" />
<property name="env.SystemRoot" value="C:\WINNT">
<property name="SystemRoot" value="${env.SystemRoot}" />
Explanation: properties are immutable. If env.SystemRoot is set from the
first line above then the second "assignment" is ignored.
Erik
----- Original Message -----
From: "Christoph Thommes" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 05, 2002 6:55 AM
Subject: Environment Variable Retrieval in Future Ant Versions
>
> I would like to read an environment variable on a Windows machine, for
> example SystemRoot.
>
> Since the environment variable retrieval in Ant is case-sensitive, I
cannot
> be sure that
>
> <property environment="env" />
> <property name="SystemRoot" value="${env.SystemRoot}" />
>
> will always return a value. I, therefore, would like to have a default
> value, if no value is available.
>
> In Ant1.4.1 I am using the following code to accomplish this:
>
> <?xml version="1.0"?>
> <project name="test_env" default="all" basedir=".">
> <target name="all">
> <property environment="env" />
> <property name="tmp.SystemRoot" value="${env.SystemRoot}"
/>
> <condition property="SystemRoot" value="C:\WINNT">
> <and>
> <equals arg1="${tmp.SystemRoot}"
> arg2="$${env.SystemRoot}"/>
> </and>
> </condition>
> <property name="SystemRoot" value="${tmp.SystemRoot}" />
> <echo message="SystemRoot: ${SystemRoot}" />
> </target>
> </project>
>
> Is the condition statement going to work the same way in future versions
of
> Ant (1.5+)?
>
> Christoph
>
> --
> GMX - Die Kommunikationsplattform im Internet.
> http://www.gmx.net
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
