release tags in java3d github

Hello again, everyone.

I need to debug the versions of Java3d and JOGL, as available here:

http://cloud.github.com/downloads/hharrison/*/*.jar
http://jogamp.org/deployment/archive/rc/v2.0-rc11/jar/*.jar

However, it is apparent that the Java3d sources have undergone some changes since the last release.  (I haven't cloned JOGL sources yet, but the same may be true there.)  How do I determine which commit to sync to?  Please forgive me if this is a git-newbie question.  I see a "tags" tab on github, but nothing there for java3d-core, at least.

On a related note, should I expect that those versions of Java3d and JOGL will work together?  Would I be better off working from the head of each?

Context:

I'm giving up on my Java Web Start deployment of Java3d and JOGL on Java 1.6 on the Mac;  Apple is determined to make javaws with 1.6 impossible, it seems.

Obviously, the way forward is with Java 1.7, and presumably I can rely on Java Web Start working there, even on the Mac.  To that end, I'm focusing on a local deployment initially, to eliminate the extra variables.  However, I'm having some difficulty getting JOGL 2.0 classes to load, doubtless through some problem with my library path.  I really need to step through the JOGL library loading code.

Thank you,

Scott

On 02/08/2013 10:00 AM, vorth [via jogamp] wrote: Yes, it's on our long TODO list to add java3d builds to Jenkins.

Right now, Harvey provides builds.

Since JOGL changes shall not harm Java3D too much - they all should work.
Of course .. there are always exceptions :)
There is still a long road to walk for us to make JOGL rock solid
on OSX w/ Java7. Pls keep in mind that Java7 on OSX is not that stable
itself due to tons of code changes especially in the AWT area.

~Sven

>
> Thank you,
>
> Scott

Java3D should be pretty easy to build directly from my master branch these days, WRT to JOGL, I tend to track the
released versions, so currently I do my testing with -rc11, nothing has really changed functionally in Java3D in awile,
so I haven't put out a new build.  Also, github stopped hosting files directly like I was doing before, so I'll either
have to start putting them on dropbox or something, or push out a repo of 'builds'...I dunno.

Harvey

Thanks, guys.

Harvey, I did make an attempt to build from source, but it looks like the ant scripts are unchanged for 5 years.  Is that what you use?  Any particular flags you set?  How do you point at JOGL classes?  I haven't dug through the ant files much yet, but you could save me an hour with a few tips, perhaps.

Sven, assuming I can get the build going locally, I'd be happy to set it up on your Jenkins server.  I use it at work and personally, quite a bit.

Scott

Harvey, never mind.  I found the build2.xml files, and worked out that you do vecmath manually, then java3d-core, and you set the jogl.lib and gluegen.lib properties.

Scott

Harvey, I hit a real snag, now.  With either JOGL rc10 or rc11, I see this error compiling java3d:

    [javac] /Users/vorth/vZome/java3d-core/src/classes/share/javax/media/j3d/JoglPipeline.java:78: package com.jogamp.common.nio does not exist
    [javac] import com.jogamp.common.nio.Buffers;
    [javac]                             ^

(and of course lots of downstream errors)

Should I be building JOGL from source, too?

Scott

You should be able to build with -rc10 and -rc11 at least...I know this is poorly documented, let me try here:

1) build,xml in both projects has been kept in case there were any remaining nuances to the build
I may want to take at a later date, but cannot be used to build anymore.  build2.xml is what I've
been using.

2) I've assumed a certain folder structure for the repos:

vecmath/
j3dcore/
j3dutils/

Where each repo is checked out into its own folder above.

It appears I just coded the relative path to the jogl2 jars, for building you only need jogl-all.jar and gluegen.jar
so relative to the j3dcore folder you need ../../jogl-rc10/jogl-all.jar and ../../jogl-rc10 gluegen.jar

look at the jogl.lib and gluegen.lib properties in build2.xml.

3) vecmath must be built first (as the vecmath/build/jars/vecmath jar is needed by j3d)

ant -f build2.xml

4) j3d and j3dutils have two-way dependency and are all built together from the build2 script in
the j3d repo.

ant -f build2.xml

I just tried with both -rc10 and -rc11 of jogl and 'Works for me' (TM)

Pop by irc if you need any more help.

Harvey

gluegen-rt.jar should be enough, you don't need gluegen.jar.

Really?  (runs off and tries)  Well I'll be damned, I swear that didn't work when I originally did that....neat!

Any pointers to the best source of what the high-level purpose of the various gluegen/jogl jars are?

Harvey

Ha!  That was it.  The build2.xml file says "gluegen.jar", but I downloaded "gluegen-rt.jar".  Thank you both!

Scott