The remote machine which is going to use the my application JAR should have the dependent JAR(needed for my app. to run) in their machine, right?I don't know what other meaning you could possibly ascribe to 'shipped separately.'
Otherwise while accessing my application JAR from the remote machine will throw exceptions?I don't understand what else you think could it possibly do.
AnanthJava wrote:Using a hard coded path is an extremely fragile way to get it working. Paths in a manifest should generally be relative.
Thanks I got it work with the classpath entry in MF with the absolute path.