Posted by utgarda on Sep 11, 2010; 8:49pm
URL: https://forum.jogamp.org/What-about-Maven-tp844816p1458592.html

Michael Bien wrote

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

Michael Bien wrote

you would have to start somewhere. Having a temporary mix of ant + maven is completely fine. As long nobody starts at the root of the tree.
JOAL/JOCL are leaves.

Yep, just put GlueGen 1.0-beta07-SNAPSHOT to oss.sonatype.org : https://oss.sonatype.org/index.html#nexus-search;quick~gluegen
Gonna update the snapshot on commits to master and deploy further tagged versions. Currently there are natives present only for linux-amd64, cause I didn't do the crossbuild yet. But you can use the new buildfile to quickly install to the local repo everything you build on your system with target "maven.install"

And yes, that's just calling maven from ant to install/deploy artifacts. Didn't touch the build itself - currently it's too much of a task for me to rewrite gluegen build from ant to maven, and no need to do it too, cause it works fine as it is. So just added maven calls to deploy created files at the bottom of build.xml

Guess I'll do it the same way for the rest of jogamp.org, but let me finish it with GlueGen first. To do it properly I need to fulfill requirements of sonatype's forge (and, for that matter, those of maven central repo ), and compose some valid and descriptive pom files. To help me do this, you can answer these questions:

   1) What are the artifacts dependencies - what depends on what? natives on gluegen.jar, or the contrary, or neither. Sorry, I don't use gluegen directly, so I don't understand that. And what does -rt and -cdc mean? Just give me a link please, I'll read and try to understand that myself.

   2) Is there some link to the BSD license version used in gluegen officially published on the net?

   3) As part of future better maven compatibility, can you guys rename your artifacts so they have the os-and-platform part of their names at the end? I mean, name them gluegen-rt-natives-cdc-linux-amd64.jar, not gluegen-rt-natives-linux-amd64-cdc.jar That would gradually simplify maven deployment, cause maven puts platform classifier at the end of filenames, and I can't change that.

Think I already know all the other info I need for now.