Talking about <exec>'s <env>, I'm confused by the current doc. Seems like using <env> once doesn't pass in current environment to sub-process, but attribute newenvironment seems to indicate the contrary. What am I missing?
And what exactly are: * the old environment, * the environment of the current Ant process? Are these two really different? Thanks, --DD --- extract from http://jakarta.apache.org/ant/manual/CoreTasks/exec.html ---- newenvironment: Do not propagate old environment when new environment variables are specified. Required? No, default is false env: It is possible to specify environment variables to pass to the system command via nested <env> elements. Please note that the environment of the current Ant process is not passed to the system command if you specify variables using <env>. -----Original Message----- From: Diane Holt [mailto:[EMAIL PROTECTED]] Sent: Friday, March 29, 2002 3:19 PM To: Ant Users List Subject: RE: How to get a Environment Variable value from Ant build file? --- "Guthrie, John" <[EMAIL PROTECTED]> wrote: > Can you "put one back" too? Like if I wanted to set LD_LIBRARY_PATH > within ant for an exec task? See the <env> nested element. Diane ===== ([EMAIL PROTECTED]) __________________________________________________ Do You Yahoo!? Yahoo! Greetings - send holiday greetings for Easter, Passover http://greetings.yahoo.com/ -- 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]>
