There are two good ways to use JOGL in an Eclipse RCP app.
Way #1: Do it like in my tutorial at
http://wadeawalker.wordpress.com/2010/10/09/tutorial-a-cross-platform-workbench-program-using-java-opengl-and-eclipse/. This is the original way where you include .dll/.so/.dylib files directly. It works, but is a bit tedious to set up because of the number of files.
Way #2: Create a separate plugin just like in Way #1, but put in native JARs instead of .dll/.so/.dylib files. In this case your plugin contains gluegen-rt.jar, five gluegen-rt-natives-<platform>.jar files, jogl-all.jar, and five jogl-all-natives-<platform>.jar files. There is one trick here: you have to add an URL resolver to your code somewhere, so it can transform bundleresource: URLs to file: URLs. I do it in my main editor control like this:
import org.eclipse.core.runtime.FileLocator;
...
public void createPartControl( Composite compositeParent ) {
JarUtil.setResolver( new JarUtil.Resolver() {
public URL resolve( URL url ) {
try {
return( FileLocator.resolve( url ) );
}
catch( IOException ioexception ) {
return( url );
}
}
} );
...
<set up JOGL GLCanvas>
}
This URL resolver is what lets JOGL find the *-natives-*.jar files from the runtime classspath of the jogl-all.jar file, which is a bundleresource: URL when running inside an Eclipse RCP app.
You'll also need to remove -Djogamp.gluegen.UseTempJarCache=false to get this to work, since the temp JAR cache is where JOGL unpacks the .dll/.so/.dylib files at runtime.
Please let me know if you have any questions or have trouble getting this to work -- I've done it many times, so it should be functional.
Locked
