Posted by utgarda on Sep 13, 2010; 1:10am
URL: https://forum.jogamp.org/What-about-Maven-tp844816p1462977.html

Michael Bien wrote

gluegen.jar is just build-time infrastructure... not needed at runtime.

So, do you think I should even deploy gluegen.jar? Would anyone want it as dependency, or it's just for the ant build?

Now deploying gluegen with valid POMs, so, when the next version arrives, it will be able to go to sonatype's staging repo or even further to maven central. I didn't dig commit histories really hard, so just put in the 2 latest most active people as developers. Maybe you want to put there some of the people who did all the coding before you, as developers or committers, to give them some credit: http://github.com/utgarda/gluegen/commit/d7eb33b02604133f2593e468393f7d56c4c50f8f#diff-2
Maybe the file requires some other editing too, so please have a look.

Sorry guys, I put your emails openly, hope those files never get indexed by nasty spammers.

Elijah Menifee wrote

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.

Yep, IntelliJ Idea does that allright.

Elijah Menifee wrote

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.

Yep, that's cool. But with properly deployed pre-built artifacts their dependencies are recoursively resolved too, so the effect is pretty much the same, and in a way even better - you have the benefit of pre-built stuff.

Elijah Menifee wrote

Of course all the work to make the existing project maven compatable may not be worth the effort for the additional benefits.

Totally. Of course, we don't know until we try it, but I'm scared even to think of doing what it takes - seems such a load of work to me.