Posted by ryanmohr on Dec 05, 2012; 6:06am
URL: https://forum.jogamp.org/ZipException-when-loading-native-jars-tp4027387p4027406.html

Sorry Sven, I totally missed your original post.  I took a look at the related posts and issues.  It would help if you could describe the jar-in-jar loader better.

For example, in Test-1 of https://jogamp.org/bugzilla/show_bug.cgi?id=522#c7 I'm surprised that the jogl jars are found under lala01_lib.  What is the full list of paths that are checked in this case?

From my understanding, the auto extraction process simply copies the required libraries out of the necessary jars into a temporary directory and loads them from there.  If that's the case, why does it matter where the native jars are as long as they're included in the jar's class path?  The application has no problem finding the jogl-related classes themselves, just the libraries.

Here's the structure of our application if it helps:

application.jar -- the application itself
lib/
   resources.jar -- all the resources the application relies on
   foo.jar -- other dependencies
   bar.jar
   jogl/
      jogl-all.jar
      gluegen-rt.jar
      ... and so on for all the required jars

Onejar apparently doesn't support subdirectories in the lib dir so we flatten the lib structure before packaging it.