Posted by ryanmohr on Dec 05, 2012; 12:09am URL: https://forum.jogamp.org/ZipException-when-loading-native-jars-tp4027387p4027402.html
There are workarounds to succeed in using Java Web Start in good conditions.
Trust me. We wouldn't be going through all the extra work to package our app natively if we got good reliable service out of web start. As I said, we've been using it for ten years.
What happens if you want to install the software on a machine that's not connected to the internet? These are serious issues we have to deal with for some of our major customers (the computers are attached to CNC machines that cost close to $100K and they don't want to run the risk of catching a virus). With a native installer it's just a matter of throwing the files on a USB key, running a virus scanner, and off you go.
ryanmohr wrote
Since the path can't be modified at
runtime
It's wrong:
I know it's wrong. That's why I said "since the path can't be modified at runtime" and why I asked for your opinion: "Would it be alright to add a new property ("jogamp.gluegen.LoadLibraries", defaults to true) that when false causes the Platform class to assume the libraries have already been loaded? That way in special cases the libraries can be loaded based on the discretion of the programmer and the Platform class can just relax."
Regardless of whether the idea sits well with you, I'm making the modifications in my own fork. It's just a matter of whether I'm going to be forced to maintain the fork indefinitely for a two line change or am going to be able to have the changes accepted back into the master.