dave madden wrote:
> <snip>...
> find classes there, but is there any more to it? Why are there so
> many .jar files? Why are some in ...java/lib, and others in (and
> under) ...java/jre/lib? Is it a Bad Idea to unpack them all into a
> master tree, then make a giant .jar containing all the .class files?
>
Well, if you're using JDK 1.2, you don't need to set a CLASSPATH
environment variable. The VM will find the classes automatically in the
default locations in that release. If you want to use add-on packages
(like JMF for example), you can take advantage of the extension
mechanism by putting the jar files in <java_home>/jre/lib/ext and then
it "just works" - as long as the jar files are world-readable (or at
least readable by your user account). If you're using an earlier release
of Java, you'll need to have all the jar and zip files containing
classes in your CLASSPATH.
Generally, you should not need to unpack the jar files, nor is it
generally a good idea to do so, as they frequently contain fairly
complex directory structures that, if altered, will cause the VM to not
be able to find the classes it needs.
--
Jeff Galyan
http://www.anamorphic.com
http://www.sun.com
jeffrey dot galyan at sun dot com
talisman at anamorphic dot com
Sun Certified Java(TM) Programmer
======================================================================
Linus Torvalds on Microsoft and software development:
"... if it's a hobby for me and a job for you, why are you doing such a
shoddy job of it?"
The views expressed herein do not necessarily reflect those of my
employer.
Sun Microsystems, Inc., has no connection to my involvement with the
Mozilla Organization.
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
