JogAmp Release [Candidate] v2.0-rc5

Dear Community & Friends,

after RC4 was tested and critical bugs were discovered in regards
  - Mac OS X (GLCanvas Applet, ..)
  - Applets  (start / stop)
  - JarTempCache usage for JOAL, JOCL and JOGL's Cg
  - JOGL's Cg JNLP test.
  - Stability and many other bug fixes.

a quick followup release (RC5) was required.

More testing is very welcome, especially w/
  Mac OS X 10.5, 10.6.4 and 10.7 [standalone / applets]

  http://jogamp.org/deployment/jogamp-current/jogl-test-applets.html

  Known Issues w/ OS X and GLCanvas/Applet:
    In JNLP mode (not AppletLauncher or NApplet),
    the GLDrawable is not valid (underlying offscreen layer).

Thank you all very much for your contributions (testing, ..).

+++

The following aliasing of URL location has been made,
ie. all are aligned to v2.0-rc5 for now.

http://jogamp.org/deployment/

    v2.0-rc5 -> archive/rc/v2.0-rc5
    jogamp-current -> v2.0-rc5
    jogamp-next -> v2.0-rc5
    webstart -> v2.0-rc5
    webstart-next -> v2.0-rc5

Developer downloads at:
    http://jogamp.org/deployment/v2.0-rc5/archive/

    Now contains sources and changelog files!

Git repositories have been tagged w/ v2.0-rc5.

+++

Even though important bug fixes for stability,
the planned features are pushed to RC6:

RC6:
  - SWT merge (proper impl. of an SWT Canvas)
  - Maven2 integration (I know .. a bit late it is already)
  - Mobile/Android autobuilds / release
  - More bugfixes
  - Update the graph package

+++

Cheers, Sven

You can install maven version of package here :
https://github.com/reyman/scriptJogamp
git clone https://github.com/reyman/scriptJogamp

I make some correction and i redploy the .jar on maven site the 26/01/2012
Sorry for inconvenience :)

There is two method to use jogl with maven :

1 - You use the script to install jar on your local maven repository

a - sh script-dl.sh
b - modify the path into script-replace.py script :
mapping_file = "<your-path>/mapping-version-current"
file_path = "<your-path>/scriptJogamp/"
c - run the python script to create file : python script-replace.py
d - sh script-install.sh

2 - You use this information in your pom.xml

<dependencies>
        <dependency>
            <groupId>org.jogamp.jogl</groupId>
                <artifactId>jogl.all</artifactId>
                    <version>2.0-b45-20111219</version>   
        </dependency>
        <dependency>
            <groupId>org.jogamp.gluegen</groupId>
                <artifactId>gluegen-rt</artifactId>
                    <version>2.0-b33-20111219</version>
        </dependency>
    </dependencies>

    <repositories>
       <repository>
            <id>thirdparty.maven.iscpif.fr</id>
            <name>ISCPIF repository</name>
            <url>http://maven.iscpif.fr/thirdparty/</url>
       </repository>
    </repositories>


I use this mapping file for  this RC5 version :
v.org.jogamp.gluegen=2.0-b33-20111219
v.org.jogamp.jogl=2.0-b45-20111219
v.org.jogamp.jocl=0.9-b29-20111219
v.org.jogamp.joal=2.0-20111219

If you see bugs, improvements for this script, your help is welcome :)

Julien Gouesse, or Sven Gothel, if you have some times to test this version, i really apreciate :) Thanks !
SR.

I will try to find some time next week to give it a deeper try.

Would be cool if we could finally have a main official jogl version on maven cenral

On 06/17/2012 10:49 AM, Danny02 [via jogamp] wrote:
> Would be cool if we could finally have a main official jogl version on maven
> cenral
>

If somebody very familiar w/ maven (you?) could support us,
then we can to this together.

Assuming:
Some may like to see the artifacts being published w/ pom files,
so applications using JOGL (etc) could be build w/ maven.

~Sven

Hi,

I'm interested, the script work for all release, but we only need to modify the name of jar generated by maven.
I think it's possible, but i don't know "how" actually.
So with this tricks the native loader created by Sven can load the jar.

What do you think Sven and gouessej about the script, the method ?
If i have some time i can modify it.




--

I see what you mean, there is still this problem in JAR naming.

I think it's not a big issue, if anyone have an idea about that ...




--