Re: trivial third party jar dependancy
Mark Space wrote:
With java -jar, you have to set the Class-Path property. For whatever
reason, java -jar ignores any classpath you specify on the command line.
This is very counter intuitive to me, but there it is.
There is a rationale for it. JARs are how you package your application to run
in a foreign environment (the user's). You have no control over the user's
CLASSPATH or if they use the -cp option correctly. To get around that, you
could write a shell script to launch the JAR, but that breaks portability, not
to mention you now have to deal with the PATH and all sorts of crap on the
user machine. If you package your application as a JAR to be run with "java
-jar" it's independent of the client environment; the application packager has
complete control of the classpath. Users cannot accidentally or maliciously
change things by substituting alternate classes into the classpath. The
-classpath option is for the user; the -jar option with manifest control of
the classpath is for the vendor.
Perfectly "intuitive".
--
Lew
"The only intuitive interface [for humans] is the nipple."