Community
Participate
Working Groups
Add better support in the UI for adding a VM to "Installed JREs" and Execution Environments" even if it doesn't run on the current machine. Bug 189486 and bug 262542 discuss instances of this problem. Another case I had recently is that JDK 1.3 doesn't run any more on recent Linux systems. Even if a VM can't run, it's still interesting to use its class libraries as compilation target on the build path (this should work even if the JRE is from a completely different platform). The only way I know to add such JREs is by creating a *.ee file with mostly dummy entries, but understanding the format of those files and adding the right dummy information is just too much work. This should be added somewhere in the "Add JRE" wizard of the "Installed JREs" page (probably as a separate wizard).
Also note that the current approach of launching the VM to detect properties can lead to issues/crashes like e.g. in the Mac case.
> *.ee file with mostly dummy entries Such a dummy Execution Environment description file is OK to set up a build path and compile against the EE (/org.eclipse.osgi/osgi/OSGi_Minimum-1.2.ee is such an example). But when you try to launch a Java Application or a JUnit test from such a project, the dummy EE is also used as runtime JRE, which obviously fails. Bug 334376 would help to ease the pain. Dummy EEs should be recognized (e.g. by the magic argument "dummy" in "-Dee.executable=dummy" ), and in that case, another JRE should be used for launching (e.g. the workspace default JRE).
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Problem is not resolved, but no time to work on this!
