Posted by gouessej on Nov 07, 2013; 3:25pm
URL: https://forum.jogamp.org/Properly-Exporting-JOGL-tp4030517p4030526.html

Yes using separate JARs including one that can be "launched" instead of trying to put everything into the same one is a good start. The fat JAR approach is useful only to reduce the time spent in OCSP requests during the deployment of signed applications using Java Webstart and with some installers that may require a single JAR for the whole application to build a self-contained bundle.

As a second step, you can include scripts and even a Java virtual machine if you don't want to rely on the JVM installed on the system.

As a third step, you can use a really complete installer to ease the setup of your application so that the end user doesn't have to run a script, it can create desktop shortcuts too for example.

Java Webstart is fine but you still depend on the installed JVM, JDT is blocked by Firefox and "trusted" certificates will become mandatory in the near future. It's very convenient when you already have several JARs, you can push automatic updates.