Posted by gouessej on Feb 26, 2013; 8:15pm
URL: https://forum.jogamp.org/ZipException-when-loading-native-jars-tp4027387p4028396.html

It would be fine to ease this approach that way:
- the developer shouldn't have to load the libraries by himself, because it can become very tricky in managed environments, especially with Netbeans RCP, when you have one class loader per module and you can't load the same native library twice in a single VM. The order in which libraries are loaded may change a bit in the future...
- the libraries should be extracted into the same directory than those we already use in JogAmp. Why reinventing the wheel?

The remaining problem is about version conflicts. What happens when an end user runs two applications using different versions of JogAmp APIs?