Posted by Elijah Menifee on Sep 12, 2010; 7:06pm
URL: https://forum.jogamp.org/What-about-Maven-tp844816p1461816.html

I agree that providing maven artifacts alone would be much easier and would probably be a good starting point.  I agree this would cover what most people in the community wants.  In fact I myself could probably get by with just the artifacts being available.

Adding an ant script to deploy the latest pull/build artifacts to your local repository for depedent projects when working on the bleeding edge as a snapshot would probably suffice.

I still think that building with maven long term might be desireable, but a lower priority.  The upsides of using a maven project pom is it provides a cross-ide project that can be used by Eclipse, Netbeans, and I believe IntelliJ.  Also instead of relying on published artifact versions for a specific platform, a maven project could depenend on another maven source/snapshot project, and descend and build the dependancy first for the local platform.  Of course all the work to make the existing project maven compatable may not be worth the effort for the additional benefits.

Michael Bien wrote

Just want to note that this are actually two distinct goals:
1. provide maven artefacts
2. build with maven

1. should be relatively easy, 2 is lots of work... really. 1. is
probably also the feature the community wants (just add project x as
dependency). I am relatively new to maven, maybe i am oversimplifying
things here, but why not start with the simple task first?