Posted by gouessej on Dec 04, 2012; 6:58pm
URL: https://forum.jogamp.org/ZipException-when-loading-native-jars-tp4027387p4027398.html

ryanmohr wrote

The purpose of using onejar is to allow us to have a single file that can
then be packaged as a native app / installer for any platform (wrapped into
an app bundle and disk image for macs, wrapped into an executable and
installer using launch4j and inno setup for windows, and linux users just
get the jar compressed into a .tar.gz).  Works great and simplifies our
deployment process.  Only thing that doesn't work is jogl.

You are exposed to bugs of Launch4J and inno setup whereas Java Web Start is reliable enough to do something similar, it's even better for updates, the end user doesn't have to download the fat JAR each time, Java Web Start can update only the modified JAR(s). We cannot support all installers.

ryanmohr wrote

I can easily skip the native jars and write my own native library loader
that detects the platforms and loads the right libs.  Just didn't want to
go to the effort if you guys had already written something that would work
for us.

Why not helping us to fix this bug? It would benefit to the whole community and you would not have to maintain a separate loader alone.

Edit.: Sven's Jar-In-Jar approach should work in your case.