I'm not sure if there're any other reasons but to me it's very obvious so one
can distinguish
${HOMEPATH} vs. ${env.HOMEPATH} as they're clearly 2 different animals, if you
will. How else Ant would know what you mean and how're you magically going to
reference the system environment w/o "env."?
Even if there was a way to comment out <property environment="env"/>, it's no
savings in memory or uncluttering your scripts!
Sorry, I really don't know if there's any other way to refer to system
environment values, maybe someone else does?
> Date: Wed, 30 Dec 2009 10:14:14 -0800
> From: [email protected]
> To: [email protected]
> Subject: RE: Reading environment variables in ant script directly
>
>
> Thank You Rez,
>
> Are u aware of why such explicit approach was taken rather providing the
> environment properties directly.
>
> It would be nice, if ant could consider to provide the environment variables
> implicitly including the conventions you mentioned on prefixing them with
> env.
>
> Regards,
> Raja Nagendra Kumar,
> C.T.O
> www.tejasoft.com
> --
> View this message in context:
> http://old.nabble.com/Reading-environment-variables-in-ant-script-directly-tp26964622p26970528.html
> Sent from the Ant - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
_________________________________________________________________
Your E-mail and More On-the-Go. Get Windows Live Hotmail Free.
http://clk.atdmt.com/GBL/go/171222985/direct/01/
