Agree that everything should use GShell.
The point of G4093 was to make the scripts in the 2.1.x release
consistent in how Java was used (some scripts used JRE/JAVA_HOME while
others used whatever was on the PATH.) I'm fine in changing this for
2.2, especially given there will only be one way (GShell) for
starting/stopping the server, launching the deployer and wsgen tools and
for client apps.
-Donald
David Jencks wrote:
Lets change the scripts in bin that don't use gshell to use gshell.
Then the helper scripts such as setjavaenv.sh will only be used for
starting gshell and I hopefully they won't need most of their current
contents.
As noted in GERONIMO-4093 I'm not OK with requiring JAVA_HOME to be
defined on systems that don't need it, and I took matters into my own
hands and restored the old behavior of using "java" if JAVA_HOME is not
defined. I'm barely literate in bash so there may well be a better
solution.
thanks
david jencks
