Richard Reynolds wrote:
"Lew" <lew@nospam.lewscanon.com> wrote in message
Yep, that's what I just said.
I gave 2 options, put the relative classpath in the manifest and
double click or "if that wasn't required" start from a script i.e. set
your jars on the classpath and execute via java or javaw as normal.
What confuses me about this statement is that Sun explicitly says you
can't put your own .jar in the classpath this way. It's rather counter
intuitive.
Quote from:
http://java.sun.com/docs/books/tutorial/deployment/jar/downman.html
Note : The Class-Path header points to classes or JAR files on the local
network, not JAR files within the JAR file or classes accessible over
internet protocols. To load classes in JAR files within a JAR file into
the class path, you must write custom code to load those classes. For
example, if MyJar.jar contains another JAR file called MyUtils.jar, you
cannot use the Class-Path header in MyJar.jar's manifest to load classes
in MyUtils.jar into the class path.