Posted by Sven Gothel on Dec 04, 2012; 5:46pm
URL: https://forum.jogamp.org/ZipException-when-loading-native-jars-tp4027387p4027396.html

On 12/04/2012 06:16 PM, ryanmohr [via jogamp] 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.

Gentlemen, I recently summarized whats possible in this regard
in this forum - pls read:
  <http://forum.jogamp.org/appbundler-jogl-jnilib-dylib-one-jar-confusion-td4027169.html#a4027245>

It would be great if you could pick that up and evaluate for your needs.

We might be able to accommodate you if proper collaboration is possible,
i.e. discussing the deployment specifications.

Please note that none of the mentioned external deployment models
are known to 'us' officially. So if this discussion should earn
some meaning - pls detail the specifications, compare it w/ what we
have w/ JogAmp and whats required. [-> Requirement management].

If the above is possible, we sure maybe able to arrange a solution.
It's not like we are stubborn :) Example: We did the same for maven2
packaging support.

Thank you.

~Sven