Surjan Singh wrote:
>
> I always thought that you _don't_ need the classpath. If you have your
> PATH variable correctly (for the release you want to use, e.g.
> /usr/local/jdk1.2/bin) then you don't need to worry about anything else.
>
> The only reason you would want your CLASSPATH set, is if you have other
> Java libraries you want your compiler/java/appletviewer to see.
>
> If you want to remove a release of the JDK just remove the folder and
> its contents.
It's correct that you don't need to set the classpath for JDK1.2. It
works in a much more sane and sensible way than it did before. If you
have a CLASSPATH set when you invoke the JVM, it is *added* to the
default one needed to make Java work. IIRC in JDK1.1 this wasn't the
case: If you had your own libraries to add, you had to define the whole
classpath.
--
Rachel
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
