Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@apache.org Received: (qmail 97550 invoked from network); 29 Jul 2002 18:40:09 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 29 Jul 2002 18:40:09 -0000 Received: (qmail 28044 invoked by uid 97); 29 Jul 2002 18:40:24 -0000 Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org Received: (qmail 28005 invoked by uid 97); 29 Jul 2002 18:40:23 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 27992 invoked by uid 98); 29 Jul 2002 18:40:22 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: From: Dominique Devienne To: "'Ant Users List'" Subject: RE: problem with environment variable Date: Mon, 29 Jul 2002 13:40:00 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I'm probably wrong, but it sounded to me that the original poster wanted to modify the environment of the shell/cmd running Ant, which cannot be done AFAIK. Modifying the registry will take effect on cmd.exe run after the change, not the one currently running Ant. And the proposed solution affects the environment of the command run only, and doesn't persist across invocations. --DD -----Original Message----- From: Hal Hildebrand (web) [mailto:Hal.Hildebrand@hellblazer.com] Sent: Monday, July 29, 2002 12:22 PM To: Ant Users List Subject: Re: problem with environment variable 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. 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 elements: It's not elegant, but it works. ----- Original Message ----- From: "Dominique Devienne" > > There's no problem. This cannot be done. --DD > > -----Original Message----- > From: TINE Houari (OBJECTIVA) [mailto:houari.tine@ca-cedicam.fr] > > > I has followed the indication given by Tibor Strausz about creation of > environment variable from Ant through . > > But, it does't work. > > > > > > > > > > Second task don't print test. What's problem. > > TINE > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > > -- To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: