This seems to be what is happening and I also believe that it makes setting the environment for exec very fragile, because it can cause unanticpated side effects. This is exactly what I've seen. Being able to add to the environment variables would be great.
Thanks, Dave Jose Alberto Fernandez writes: > I think Runtime.exec replaces completely the current environment > with what you pass, as oppose to adding to the environment. > > This to me is a major BUG on the API making Runtime.exec() with environment > almost useless. How can anyone ADD to the environment of a call if there is > no way to know what was there before? > > Am I off the ball here? Is this a bug in certain implementations or a bug in > the spec? Is the spec not precise enough? > > Jose Alberto > > > > -----Original Message----- > > From: David Forslund [mailto:[EMAIL PROTECTED] > > Sent: Thursday, August 10, 2000 10:27 AM > > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > > Subject: Re: <arg> > > > > > > I still don't see the environment passed, but I do see that > > if I set the > > PATH variable, my CLASSPATH environment > > must not be passed. I have to set both PATH and CLASSPATH to get my > > environment to my application. > > I guess I don't understand why this needs to be the case. > > > > Dave > > At 05:34 PM 8/10/00 +0200, Stefan Bodewig wrote: > > > >>>>> "DF" == David Forslund <[EMAIL PROTECTED]> writes: > > > > > > DF> I can't get the -verbose flag to tell me what was > > actually passed > > > > > >I've just checked in a version that should list the > > environment passed > > >to the sub process. > > > > > >Stefan > >
