We haven't found a way to do this from the command line, but you can do this with specialized code.
See JRegistryKey: http://www.beq.ca/tech/Products/jreg_key.shtml It's easy to use the above to create a custom Ant task which will permanently manipulate the windows registry, such as path and environment variables. However, the Ant process executing the task, and any spawned executables don't inherit the environment. <sigh> There apparently is some Win32 call which will force an update of the environment variables, but I haven't followed the bread crumbs to find out if there is such a thing. Another option is to use nested <env> elements: <exec dir="${basedir}" executable="cmd.exe"> <arg line="/c set"/> <env key="test" value="tst" /> </exec> It's not elegant, but it works. ----- Original Message ----- From: "Dominique Devienne" <[EMAIL PROTECTED]> > > There's no problem. This cannot be done. --DD > > -----Original Message----- > From: TINE Houari (OBJECTIVA) [mailto:[EMAIL PROTECTED]] > > > I has followed the indication given by Tibor Strausz about creation of > environment variable from Ant through <exec>. > > But, it does't work. > > <exec dir="${basedir}" executable="cmd.exe"> > <arg line="/c set test=tst"/> > </exec> > > <exec dir="${basedir}" executable="cmd.exe"> > <arg line="/c set"/> > </exec> > > Second task don't print test. What's problem. > > TINE > > -- > 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]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
