This seems like the only way to go for now. If ant had an "include" command, I could define some variables which would take care of this. Otherwise, I'm stuck with system dependent code embedded in ant.
Dave Jose Alberto Fernandez writes: > Actually, as awfull as it is. This may be the most portable thing we can do. > It would really solve the problem for good. If it is only executed once the > impact should be quite low. > > The things on has to do .... :-( > > Jose Alberto > > > -----Original Message----- > > From: Jesse Glick [mailto:[EMAIL PROTECTED] > > Sent: Monday, August 14, 2000 10:41 AM > > To: [EMAIL PROTECTED] > > Subject: Re: <arg> > > > > > > Stefan Bodewig wrote: > > > As others have pointed out, it's a all or nothing thing. > > Once you send > > > any environment variables to the subprocess, you have to > > set them all. > > > > > > I've put a warning into docs/index.html about this when I documented > > > <env> two days ago. I don't think Ant has a way to circumvent this. > > > > If you wanted to be perverse I guess you could have Ant > > lazily run as a > > subprocess "env" (Unix) or "set" (Windows; is this right?), gather the > > results, parse them, and use them as defaults when <env> vars were > > specified in exec tasks (in Execute.setEnvironment). A heinous > > workaround for a dumb JDK bug. > > > > -J. > > > > -- > > Jesse Glick <mailto:[EMAIL PROTECTED]> > > NetBeans, Open APIs <http://www.netbeans.org/> > > tel (+4202) 3300-9161 Sun Micro x49161 Praha CR > >
