We are running JBoss 4 versions on Windows platforms. We always make sure to set the JBOSS_HOME and JBOSS_DIST (redudant?) environment variables on our production machines. However, on test machines we frequently have several different versions of JBoss installed. These seem to work fine, despite the wrong paths being set in the JBOSS_HOME, etc. environment variables.
From looking at the startup scripts, it seems that JBoss on windows simply ignores and overwrites the JBOSS_HOME variable, while the .sh script will use it, if it is non-empty.
So is there any reason to continue setting these environment variables in windows? Is it primarily so that other applications can find JBoss?
Regards,
Jeff
