Posted by Xerxes Rånby on Aug 18, 2014; 7:34pm
URL: https://forum.jogamp.org/missing-jar-file-from-JOGL-folder-tp4032820p4032823.html

Please read the deployment documentation
the most common case is described in the deployment, userguide and wiki here:
https://jogamp.org/jogl/doc/deployment/JOGL-DEPLOYMENT.html#NativeJARFiles
https://jogamp.org/jogl/doc/userguide/index.html#automatednativelibraryloading
http://jogamp.org/wiki/index.php/Downloading_and_installing_JOGL

rt = runtime, indicating you want to use them at runtime.
gluegen-rt.jar <- use this at runtime!
gluegen-android.jar <- use this when you perform android builds.
gluegen.jar <- this jar is to be used to let "Gluegen" generate new java glue code using C header files. in your case you shall _not_ add this jar to the CLASSPATH at runtime because then gluegen will try to load the natives using the gluegen prefix instead of the gluegen-rt prefix.


to summarize: when deploying only include the following jar on the classpath
gluegen-rt.jar

..and have the following jars in the same folder:
gluegen-rt-natives-android-armv6.jar
gluegen-rt-natives-linux-amd64.jar
gluegen-rt-natives-linux-armv6hf.jar
gluegen-rt-natives-linux-armv6.jar
gluegen-rt-natives-linux-i586.jar
gluegen-rt-natives-macosx-universal.jar
gluegen-rt-natives-solaris-amd64.jar
gluegen-rt-natives-solaris-i586.jar
gluegen-rt-natives-windows-amd64.jar
gluegen-rt-natives-windows-i586.jar


JogAmp also support some additional types of deployment:

Eclipse is a "special case" because Eclipse adds its own classloader to your executable that can load jars from inside a single jar and other tricks.
Multi-Jar, Fat-Jar, SvgExe, Eclipse (onejar) all described in:
https://jogamp.org/wiki/index.php/JogAmp_JAR_File_Handling