Posted by rthur on Mar 12, 2014; 3:23pm
URL: https://forum.jogamp.org/Dealing-with-the-outdated-java3d-libraires-on-Mac-tp4031866p4031868.html

Hi Julien,

I guess we'll have to settle for renaming the packages to avoid the conflicts - it seems messy, but at least it'll work.

I've written a simple class loader that inverses the Java class loader chain - it checks first if the class is available in our fat JAR, and only calls it's parent class loader if it can't find it.
This works fine for loading our classes in, unfortunately the jvm seems to be using a different class loader for actually verifying the signature of the files, and not our own.

Cheers,

Arthur