Description James Edwards 2011-09-13 15:23:18 EDT

Build Identifier: 20110615-0604

I am using JOGL in my program.  I created a User Library for JOGL with the necessary jars and native library paths for those jars.

If my JOGL User Library is on the build path of a project, java.library.path arguments for its native library paths show up in the launch command, as well as the jars in the classpath.

However, if my JOGL User Library is not on the build path, but instead added to a launch configuration's classpath, the native library paths aren't included in the launch command--only the jars are included in the classpath.

This is confusing and inconvenient.  I am trying to launch from a multiple project setup that necessitates using the launch configuration instead of the build path to include the JOGL jars and native libraries.  The native library paths of User Libraries added to a launch configuration (in the Classpath tab) should be included in the java.library.path of the launch command.

Reproducible: Always

Steps to Reproduce:
1. Create a user library (in Preferences) that contains at least one jar with a native library location.

2. Create a project and add the user library to its build path.

3. Create a main class.

4. Create a launch configuration for the main class.  Run it and verify that the user library jar is included in the launch command classpath and the native library location is included in the launch command library path.

5. Now remove the user library from the project's build path.  In the launch configuration dialog, go to the Classpath tab and add the user library to the classpath.

6. Run the launch configuration again and you will see that the native library location is not included in the launch command library path.