Campbell Ritchie wrote:That classpath in the manifest looks suspect.
In particular the back-slashes. Try using ordinary slashes to separate files.
Also I notice you're using the Java 6 version of the classpath which accepts "*" to mean "all jars in the directory". Perhaps that doesn't work in jar manifests. Anyway you've only got one helper jar so it shouldn't be too hard to name it specifically in the manifest.
Each Time I am told the Dependency from sandhi.jar is missing.
Did you know that what you have put there means that if the jar file is in directory X, then you need have a directory X/lib containing the sandhi.jar? That's different to your example where you used the -classpath option; in that case the "./lib" is relative to the current working directory.
Actually the Tutorials clarified something which I had been unclear for a long long time.
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.
So that implies their is no native out-of-the-box mechanism in Java to read jar from within the jar.
And yes when my java - jar myjar.jar were working , it was located on the same folder which also had the /lib folder.
But moving the myJar.jar to another place, the jar invocation didnt work.
Thanks all for your help, so I have now learnt a important tip on classpaths in Jar Files.