contribution - maven deploy: some pom and a shell script

Hi. I am using JOGL in an app and I use maven for building, packaging and distributions.

I would like to help you make a maven deploy of jogl on java.net repository. I will use maven just for the deploy, starting from builded jars.
The main issue is related to native libraries. See here:

http://download.java.net/maven/2/net/java/dev/jogl/

If you are familiar with maven, you will see that my plan is to create a different artifact for each native version of the jar. Every native artifact will depend upon the common jogl.jar that depends upon gluegen.
There is just linux-i586 example but just some lines in the script and everything is done :slight_smile:

My first issue is: gluegen version used in recently 1.1.1 branch is always the last releas on gluegen.dev.java.net or is a build from cvs?
The second one: there are any problem in using the webstart signed jar in a non webstart launcher? If so, I cannot use jogl.jar taken from the webstart zip…
The third: I think I resolve with some trick. I need to put exploded native jar in a folder that is in the path in order that JVM find them. I do not still know if maven has such an automation, I can always use an ant task for this job. Or, given that they are just needed at runtime, I can put the un-jar operation in the start script.

I am also asking some advice to maven2 community, you will see the conversation here when it will be archived…
http://mail-archives.apache.org/mod_mbox/maven-users/200712.mbox/browser

Thanks, bye.

Ok, I finish a part of the work, that is install gluegen-rt and jogl on repo, for three pltform.

http://download.java.net/maven/2/net/java/dev/

Now in a local project I can add a dependency to just jogl-linux-i586 to get all the jar I need. This way:

	<dependency>
		<groupId>net.java.dev.jogl</groupId>
		<artifactId>jogl-linux-i586</artifactId>
		<version>1.1.1-rc6</version>
	</dependency>

There are some folders to delete:
http://download.java.net/maven/2/net/java/dev/jogl/jogl-parent/
http://download.java.net/maven/2/net/java/dev/jogl/jogl/${parent.version}/
http://download.java.net/maven/2/net/java/jogl/

these are wrong experiments, I will ask on the proper mailing list, just ignore them.

I’ll let you know about how to create multiple distribution packages.

Thanks for doing this. I’ve been meaning to learn Maven but I think this will be a big help to developers, especially if you can provide more documentation on it and make the installation experience really smooth into the various IDEs.

Please feel free to file bugs with the JOGL Issue Tracker if you would like us to do things like modify our web pages to point to documentation or incorporate the documentation directly.

It’s always the latest release on gluegen.dev.java.net.

No problem doing this.

It sounds like you already resolved this above.

Sorry for resurrecting this thread from its grave, but the part where the jars with native libraries are “exploded” is still missing. Did anyone ever find out how to solve that?

I did find something similar for the GWT maven plugin: http://gwt-maven.googlecode.com/svn/docs/maven-googlewebtoolkit2-plugin/setup.html but I haven’t been able to adjust it to the JOGL situation (yet).

Any suggestions/help would be welcome ;D