That's an improvement. At least changes to environment variables would be guaranteed to be undone. Other changes made, such as net commands that Jan used in his example, would still be a problem.
-----Original Message----- From: Matt Benson [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 05, 2005 10:56 AM To: Ant Users List Subject: RE: Ant should have an ext directory --- "Dick, Brian E." <[EMAIL PROTECTED]> wrote: > Windows has dll hell. Java has jar war. > > If you press ctrl-c while running ant, the > antrc_post.bat file does not run. In this case, any > environment changes made by antrc_pre.bat will not > be undone. Yuk. I have long wondered about these batch files, but not a lot b/c I use cygwin (whew). However, inspired by this thread, I have just had a look and it struck me as odd that antrc_pre.bat and antrc_post.bat are called outside the confines of the (conditional depending on Windows NT or a derivative OS) environment scoping block delimited by the setlocal and endlocal commands. I would venture to say that most Windows Ant development is being done on NT, 2k, or XP and I would venture further to say that if it isn't it probably should be. All of which leads me to think ant.bat possibly should support %HOME%\antrc_local.bat which will be called after setlocal and will be immune to the Ctrl-C issue raised by Brian. Thoughts? -Matt __________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
