Jogamp Versioning and Releases

Version Fingerprint
You can get the get the source code via git, hence all references of a JogAmp module version boils down to:


 * module base version
 * git commit sha1 hash
 * hudson build number and build id
 * module OS and ARCH

artifact.properties
The version fingerprint is available in the artifact.properties file: gluegen.build.number=200 gluegen.build.id=2010-11-09_22-30-24 gluegen.build.branch=master gluegen.build.commit=92e1e8b24d128e08f13b05bd630ad7b0bf1cbf9f jogl.build.number=209 jogl.build.id=2010-11-09_22-35-00 jogl.build.branch=master jogl.build.commit=4ea473a2cbf59fcbd8e82d26da389cd8c2b4a291

We deploy artifacts.properties in the online build folder and within the platform ZIP archives.

JAR Manifest
The version fingerprint is also included within each JAR Manifest file: Manifest-Version: 1.0 Ant-Version: Apache Ant 1.8.0 Created-By: 1.6.0_21-b06 (Sun Microsystems Inc.) Specification-Title: Java Bindings for OpenGL API Specification Specification-Version: 2.0 Specification-Vendor: JogAmp community Implementation-Title: Java Bindings for OpenGL Runtime Environment Implementation-Version: 2.0-b209-20101110 Implementation-Branch: master Implementation-Commit: 4ea473a2cbf59fcbd8e82d26da389cd8c2b4a291 Implementation-Vendor: JogAmp community Extension-Name: javax.media.opengl Implementation-Vendor-Id: com.jogamp Trusted-Library: true

You can also verify the hudson build and test on our hudson server. Here is the hudson report for the above mentioned build 209, which also links directly to the github source code repository.

Each module has also a base version, like major and minor, ie 2.0, which we may change to emphasize major feature and API changes.

Releases
Releases follow the above mentioned versioning scheme.

Here you can find information about the build locations.