I've followed the thread on mavenizing Java 3D. What's the current status.
I'm trying to modernize some legacy code that uses Java 3D. I'm developing on Mac OS X Mavericks. (Not yet El Capitan, so I don't think I have the problem with the old J3D jars in /System/Library/Java/Extensions. At least they're certainly not there.)
I have Maven dependencies for the jogl-all-main and gluegen-rt-main, both version 2.3.1 Plus Maven dependencies for j3d-core, j3d-core-utils, and vecmath, all version 1.3.1.
It compiles fine, but gets a runtime java.lang.UnsatisfiedLinkError: no J3D in java.library.path.
Is there any way to fix that?
I might add that though I'm developing on OS X, my ultimate target is Windows, if that makes any difference. When last checked, I get the same "no J3D" error on Windows too.
You must use the very latest version of JOGL to make it work (currently 2.3.2). You mustn't use conflicting versions of Java3D. I remind you that we maintain only the version 1.6.0 and this Mavenization will be probably ready for the version 1.7.0. We don't maintain the versions 1.5.2 and earlier, it's explained in the sticky note and I advise you to read my tutorial. The next version, which we'd like to push on Maven Central, uses different package names, it has absolutely nothing to do with the absolutely obsolete version of Java3D (1.3.1) that you obtained elsewhere.
Thanks. I got it working using the latest 1.3.2 Java3D and 2.3.2 jogamp jars.
Java3D 1.3 requires JOGL 1. You probably meant that you got it working using JOGL 2.3.2 + Java3D 1.6.0.
J. Tolliver wrote
Do you have any timeline guestimate for when 1.7.0 will be ready for Maven?
The source code is ready. I'm not a Maven specialist, I think that we'll upload Java 1.7.0 pre 1 on our Maven (JogAmp) development repository before uploading it into Maven Central. I have no estimate. I'll have much time next month. If I had much more experience on Maven, I could do it now.