Community
Participate
Working Groups
While Java programs cannot access environment variables, jni dlls and libraries can. The behavior of some commercial instrumentation packages, such as Compuware NuMega's DevPartner Java Edition v3.0, are entirely configured via environment variables that are read by a jvmpi dll these products load using the -Xrun option. Even if environment variables are not revealed on a launch configuration tab, the ability to programatically set them through the IVMRunner interface would greatly facilitate interacting with such (jni) programs and avoid needless customization or copying of JDT logic or resorting to jni dlls loaded within Eclipse. Please consider extending the IVMRunner interface with an overloaded "run" method that accepts an environment array passed to AbstractVMRunner "exec" or some equivalent mechanism.
Although this could be added as a non-breaking API change (2.1 does must be backwards compatible with 2.0), it would be a breaking change in terms of behavior. We would need to add env vars to the VMRunnerConfiguration, but it would be up to the implementations of IVMRunner to know they exist - and existing implementations would know to honor the setting. Marking as "later" for now.
Open for 3.0
Jared, do you plan to add env vars to the java launch configs?
Yep. Support for variables will be added to JDT and Debug launch configs once the generic support is finished. *** This bug has been marked as a duplicate of 10035 ***
