Cees de Groot wrote
> It's cleaner to set CLASSPATH in a wrapper script, of course, but
> often this only is feasible for a deployment situation. When
> hacking/developing, you want to have all stuff at your fingertips.
>
Cees,
i agree with you, there are many ways to do this, and it is ok when you
know what it is doing. for myself i use a script which launches jdk102,
116, or 117 as required and with various classpaths...
the thing is, when someone writes to the list saying they cannot get the
jdk to work out of the box..
then they are better off to go with the
"standard default and recommended by the makers - no classpaths"
setup, at least until they get it working...there are so many different
ways people can configure their installations, it will be very hard for
they and anyone else to diagnose a problem and provide help, if they
start off with a non-standard setup
regards
jim watson
