Why can't one obtain the PATH variable (or others) that ant has and
optionally add to that environment for a exec task? Can this be done portably?
Conor MacNeill writes:
> Louis,
>
> > I don't think you can make any portable assumptions about
> > java.library.path. Unless someone can point to a specification,
> > I believe it's safer for the scripts to explicitly pass the current PATH
> > as a system property ("ant.system.path" or something) on the command
> > line.
> >
>
> I agree that we cannot rely on java.library.path. However I wonder if
> passing in the Path as an ant property is the start of a slippery slope
> where we end up trying to pass the whole environment into ant :-) Currently
> we have
>
> ant.home
> jikes.class.path
>
> We probably could add what you suggest, but what else (wheeeee down we go
> !!)
>
> Conor :-)
>
>
--
David Forslund Voice:(505) 665-1907
Advanced Computing Laboratory, MSB287 FAX: (505) 665-4939
Los Alamos National Laboratory EMAIL: [EMAIL PROTECTED]
Los Alamos, NM 87545 WWW: http://www.acl.lanl.gov/~dwf
