How to use the classpath defined in a manifest file when debugging

Question

Using Jdeveloper 10.1.3.3.0 (or any version)
I'd like to be able to debug using an executable jar which specifies my classpath and main class, without having to manually add all the jars to my debug configuration. Is there a way the debugger can extract that information from the manifest?
The set of jar files included in my classpath varies depending on which client configuration the client wants to run and we could potentially have a hundred different configurations so there isn't an easy way to manage static libraries. Currently I have to open the jar, extract the manifest and manually add the jars so I can debug. Which is really painful when the configuration can change each time I run. The manifest and jar file are created at runtime based on what client configuration the user is trying to run and there can be multiple versions of a jar file in the directory with mangled names - so I can't just include all the jars.
Any ideas?

Answer 1

Run the program from command line, this way you will see the errors, if any.
example.: java -jar theJarfile.jar
I was successful in creating a comm application. I placed the win32com.dll in the same directory of my application jar file and all worked.
I also extracted the comm.jar , and jar'd my app with the extracted comm files to make one jar.
I also had a fileWriter() to get the clients jre path and my app would write the javax.properties file to the correct place.
It took me severel weeks and late nights to accomplish this, but it was all necessary to be able to install only my app, and not a bunch of api's that were needed.