https://forum.jogamp.org/Problem-with-GLProfile-and-jogl2-rc2-tp3447491p3471073.html
On Tue, Nov 1, 2011 at 4:34 PM, Sven Gothel [via jogamp]
<[hidden email]> wrote:
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).
Ok, and i replace into the pom.xml the version by a keyword/var your replace with your bash :)
>
> 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.
The version is 2.0-b424-20111018 for gluegen
and 2.0-b526-20111018 for jogl
and 0.9-b455-20111018 for jocl
and 2.0-20111018 for joal
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 ?
Yes when i create a project which contain a jogl-all (for example) dependecy, if i want to deploy my project after, i need to create a jar which contain all dependency for my project (jogl, gluegen, and all dependencies for the project).
At runtime execution, my program load jogl, but jogl doesn't find the good jar, because maven download the jar dependency with version and arch, and your loader need a simple jar like jogl-all.jar, and not a jogl-all-*.jar with * = anything. Can you force your script to detect the version, or to ignore the version when it try to load the jar ?
Thank you.
Thanks :)
SR.
~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."
>
To unsubscribe from Problem with GLProfile and jogl2-rc2,
click here.