, September 28, 2005 6:16 AM
To: Ant Users List
Subject: RE: Problem with Environment Variables on Win2000
Thanks for testing it. After I posted, it started working on my Win2000 box
as well so it's strange.
Actually, this is not a new problem for me; I've run into it several times
over the l
Thanks for testing it. After I posted, it started
working on my Win2000 box as well so it's strange.
Actually, this is not a new problem for me; I've run
into it several times over the last couple of years.
On windows, sometimes it works and sometimes it
doesn't. I thought that this time it was
It works on XP.
--- rant.bat
setlocal
set foo=bar
call ant
echo on
Endlocal
--- build.xml
env.foo is ${env.foo}
--- output
C:\Projects\My Tools>rant
C:\Projects\My Tools>setlocal
C:\Projects\My Tools>set foo=bar
C:\Projects\My Tools>call ant
Buildfile: build.xml
[echo] env.fo
Perhaps a better way to accomplish the same thing would be to pass in
the value of the property on the command line in your wrapper scripts
like so...
ant -Dsomeproperty=somevalue target
This should work fine on both win and unix.
-Rob A
> -Original Message-
> From: Jason [mailto:[EMAIL
