Alternate drives in Jar file Class-Path attribute

Hello, all. I am working on a project that I would like to package into a single jar file for simple execution. At my place of work classes from EJB are stored on a different drive from where I am doing the development. I am having trouble accessing those classes from the Jars I am creating. When I try the following manifest:

Main-Class: MyPackage.MyClass

Class-Path: U:\someFolder

the application will not start, saying that MyPackage.MyClass cannot be found. This is despite MyPackage.MyClass being properly packaged into the Jar file, as verified by a jar t operation. When I leave off the drive letter in the Class-Path attribute:

Main-Class: MyPackage.MyClass

Class-Path: someFolder

the application starts and executes properly right up until a class from someFolder is needed, at which point exceptions begin to be thrown.

Any ideas will be much appreciated!

John Todd

[931 byte] By [proftodda] at [2007-11-27 7:35:46]
# 1
I was eventually able to find the answer to my own question: Jars do not accept absolute paths at all, only relative paths. Thus, the alternate drive approach will not work. Fortunately I was able to find an alternate solution.John Todd
proftodda at 2007-7-12 19:16:23 > top of Java-index,Desktop,Deploying...