Posted by Elijah Menifee on Aug 23, 2010; 4:08am
URL: https://forum.jogamp.org/What-about-Maven-tp844816p1284007.html

I agree Time is a tight resource....

I was looking at accelerated graphics frameworks for a Java based game I was planning on creating, and decided to learn maven for my managing my project.  I was disappointed to find that the current versions of jogl and/or java3d were not in maven, only old versions...

So now I have decided that my spare time could best be spent converting jogl to build under maven, so that eventually it can be maintained / built / referenced by other maven projects.  Since at the lowest level everything seems to depend on gluegen I have forked that project, with the intent of branching to creating a pom file, and rearranging the source and dependencies to match a standard maven project.

Hopefully I can make this work...and hopefully I can then follow up by making jogl into a maven project that depends on the gluegen maven repository.  At this point i am hip deep in learning maven and git along with how everything in gluegen builds and fits together.

As far as plans for the branch I understand that git properly handles symlinks (on systems that support them) so I was going to build a new directory structure that symlinked back to the normal repository build / layout files so that upstream changes would easily merge, and once I got it working with symlinks and accepted, hope to re-factor the structure up a level to make it the default build routine by actually replacing symlinks with original files at new locations...( that step might be a pain for other developers...not sure how git handles refactoring / code location changes during a merge )

In addition to the article about unpacking and moving libs around at http://buildanddeploy.com/node/14, I came across another article about a maven plugin for JNI stuff that puts the lib files under the jar's META-INF directory with a special library loader class that would pull the lib as a resouce file, save to a temporary location, then use System.load("path").  I think this is similar to what JavaWS does with JNLP's that reference custom JNI code...

So assuming I have not bitten off more than I can chew, and you are patient enough Kraft, you may eventually get an up-to date maven build for jogl...