Posted by Xerxes Rånby on Jul 10, 2013; 9:28pm
URL: https://forum.jogamp.org/Atomic-jars-in-Maven-Central-Gradle-build-system-tp4029555p4029556.html

I tested your jgl project. it looks like you got some steam having converted ~25 of the ~60 http://www.oglplus.org/oglplus/html/examples.html already!
Setup was a breeze with gradle "installed".

git clone https://github.com/jjzazuet/jgl
cd jgl
../gradle-1.6/bin/gradle tasks
../gradle-1.6/bin/gradle test
#and observe GLTestShell launch the nice  T025RecursiveTexture example.

../gradle-1.6/bin/gradle eclipse
#and get a correctly setup eclipse project to import and play in.
The other 24 examples can be run by tweaking org.jgl.swt.test.GLTestShell


I would be happy if the default build of jgl focused on portability by using the current gluegen-rt-main and jogl-all-main version 2.0.2-rc12 from maven central; ideally make jgl run on all platforms JogAmp support. It is good that jgl initially focus on GL3 core profile since it enable minimal changes in order to become both desktop and mobile portable by adapting the code for GL2ES2 profile. Switching SWT with NEWT would also improve portability and allow jgl use on mobile platforms such as Android.

Surely the minimal atomic deployment is cool to reduce footprint. Keep that as an option in gradle for minimal footprint deployments targeting a single platform. IMHO atomic deployment is mostly useful for targeted deployment inside application stores/embedded systems when you know on forehand that the application will only be deployed on a specific os, abi  and arch.

Have you considered a license for jgl or do you intend to release it under public domain?

If you like send a short summary and a reference image that we may use on the JOGL page to promote your project: http://jogamp.org/jogl/www/