Posted by Sven Gothel on Sep 18, 2012; 7:16am
URL: https://forum.jogamp.org/Java3d-1-6-0-pre3-released-tp4026211p4026213.html

On 09/18/2012 09:00 AM, hharrison [via jogamp] wrote:
> - Update for API changes made in JOGL2-RC10, now requires JOGL-rc10 or newer.

Great stuff.

Maybe it's time to add one jenkins job for building java3d ?
Sorry for being silent on this one for a while, but the last endeavors
of SIGG and FBO/OSX stole some of my communication time.

Instead of making java3d's build environment force to match our gluegen/jogl
procedure etc .. we may simply try to squeeze it in and collect
the required artifacts with the aggregation job later on.

I guess we can drop one java3d 7z file in
parallel to our jogamp-all 7z one.

How about unit tests? Sorry, I guess I have flushed my memory with all the
details you probably already told me.

IMHO it would be best if you help me w/ setting this up,
hence a tight communication for 'a few hours' could be helpful.

I would need to know:
  - your repos (I guess your github is fine?)
  - specific build instruction required ?
  - specific build order required ?
  - specific unit test processing required ? (data ?, ..?)

Then I would like to give you a user account at jogamp.org
so you can push your changes there as well.

The compatibility matrix is pretty simple: Everything in same branch
must be able to work together. Currently we maintain 'master' and 'rc'
and they are usually equal. 'rc' only exist to differentiate regular test
builds with release candidate builds.

Well .. I if you agree .. I can give it shot.
Ofc .. I will do this with the tip of 'master'.

~Sven