Posted by Sven Gothel on Nov 01, 2011; 3:34pm
URL: https://forum.jogamp.org/Problem-with-GLProfile-and-jogl2-rc2-tp3447491p3471007.html

On Tuesday, November 01, 2011 04:21:24 PM reyman [via jogamp] wrote:
>
> No problem, i'm ready and ok to integrate the generation of the pom in your
> deploiement script :)
>
> But at this time the simple example of jar we deploy on maven.iscpif.Fr
> doesn't work because the jar in the archive contain the both the version and
> the arch in his name, for example we have jogl-natives-amd64-2.xx.xx.jar

the version can be encoded in the URL,
ie where we drop/deploy the JARs on jogamp.org (or wherever).

>
> The loader you create doesn't find the jar in our assembly jar, so we cannot
> continue without your help on this problem :)

ofc I like to to change as little as possible in our current deployment scheme,
however .. if it's required.

Please point me to the latest version of your desired maven files
you like to see integrated.
This way I can understand the issue a bit better and maybe we can find a compromise.
Looks like there are 'runtime' maven dependencies/issues besides the 'compile time'
dependencies ?

Thank you.

~Sven

>
> Gouessej suggest you modify the loader of jar; like this :
> " Maybe the automatic loader could be modified so that it looks for the
> Mavenized JARs as it knows its own version of JOGL. Then, installing a
> project as a Maven project in Eclipse would be quite simple.
> com.jogamp.common.util.JogampVersion knows the implementation branch and the
> implementation commit, it should compute the name of a Mavenized JAR and
> look at it if jogl.all.jar is not found."
>