Posted by jmaasing on Nov 07, 2013; 1:48pm
URL: https://forum.jogamp.org/Properly-Exporting-JOGL-tp4030517p4030525.html

I think the "executable" jar is a good start (avoid the fat-jar approach like gouessej say).
I have been using that approach for years in a swing application. I put the required jars in a lib-directory beside the executable jar, then put classpath: lib/xxx.jar in the manifest attribute.
I distribute the application as a zip-file, the user unpacks the zip file and can run the executable jar.
The next step I did was to include lancher scripts/binaries in the zip file but they all in essence just run "java -jar" and are easy to create when you have a working "executable" jar.

Java Web Start is a very good alternative, the reason I didn't use that is when I started that project JWS didn't exist :)