On Wed, Sep 8, 2010 at 10:51 AM, Aldo Bucchi <aldo.buc...@gmail.com> wrote: > Hi Tim, > > On Wed, Sep 1, 2010 at 6:57 AM, Tim Haynes <tim.hay...@openlinksw.co.uk> > wrote: >> On 29/08/2010 10:47, Aldo Bucchi wrote: >>> * Do I have to export the env variable to the system? >> >> Yes. Otherwise it's not an environment variable, it's a shell variable.
I believe you guys are confused because Aldo's example was on Windows (he is using ";" as PATH separator in the example), in which the "set" command does set an env variable, AFAIR. Tim response was based on a Unix system (he is talking about .sh files) in which you need to use the "export" command. So, AFAICS, it is still unclear why virtuoso is not honoring CLASSPATH in Aldo's Windows setup. > In that particular system I didn't want to set any env variable because I > have more JVMs running. That should not be a concern. At least on Unix env variables are not global, just inherited from parent process to child process. As it is also the case on Windows [1]. [1] http://msdn.microsoft.com/en-us/library/ms683463%28VS.85%29.aspx -- Leo Soto M. http://blog.leosoto.com
