Java3d 1.6.0-pre3 released

- Update for API changes made in JOGL2-RC10, now requires JOGL-rc10 or newer.

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

I just pushed out the most stripped-down ant scripts I could with the latest release, if you look on the master branches of the vecmath repo and the j3dcore repo, they are checked in as build2.xml.

Could you perhaps take a look and tell me what changes they need so your jenkins instance can pick them up?

My current setup:

vecmath, j3dcore and j3dutils repos get checked out in subfolders named

vecmath/
j3dcore/
j3dutils/

vecmath needs building first, the target is 'jar' in build2.xml

the build2.xml in the j3dcore repo builds both the core and the tools (leftover from what I inherited) the
one part that will need adjustment is finding the jogl2 and vecmath jars to build against, they are set as:

  <property name="vecmath.lib"       location="../vecmath/build/jars/vecmath.jar"/>
  <property name="jogl.lib"          location="../../jogl-rc10/jogl-all.jar"/>
  <property name="gluegen.lib"       location="../../jogl-rc10/gluegen.jar"/>

The build scripts I just checked in are pretty trivial, but if you have any questions, just ask.

Harvey

Sorry, missed the other part of your message.

As for unit tests, really don't have any per-se.  There are some rudimentary unit tests for vecmath back on the
java.net site I could import and get setup.

The rest are mostly trivial 'examples' from the java3d-examples svn repo on java.net, not really amenable to
unit testing I'm afraid. :-(

On 09/18/2012 09:30 AM, hharrison [via jogamp] wrote: Sounds great and simple enough for me to give it a try.

our build node FS layout would be:
  gluegen/
  jogl/
  vecmath/
  j3dcore/
  j3dutils/

since you don't object, I guess we can add all artifacts of those three to
one 7z package file, containing the JARs ..

later on we can refine it and make it better, if required.

great.

if you can send me your 4k ssh public key (keygen -b 4096),
then I will make you an account, so you can push your source,
which shall kick of a build in the future.

~Sven

>
> Harvey

Thanks, I hope building Java3D is less painful now.