Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 165771

Summary: [jres] Eclipse runtime jre is always added to the Installed JRE even same JRE is defined by the extension org.eclipse.jdt.launching.vmInstalls
Product: [Eclipse Project] JDT Reporter: Eiji Morito <eiji.morito>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: hinaba
Version: 3.2.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
plugin to reproduce the problem
none
proposed patch none

Description Eiji Morito CLA 2006-11-24 06:42:55 EST 
Even if installed JRE is defined by extension org.eclipse.jdt.launching.vmInstalls, eclipse runtime jre (jre which eclipse is running) is added to the Installed JRE. 
This happens even the location of JRE are same.

I think the eclipse runtime jre should be added to the Installed JRE only if there are no other installed JRE defined, or only if there are no other installed jre with same location.
Comment 1 Darin Wright CLA 2007-04-23 12:09:31 EDT 
Not planned for 3.3
Comment 2 Eiji Morito CLA 2008-09-29 21:56:10 EDT 
Created attachment 113828 [details]
plugin to reproduce the problem

I attached an sample plugin to reproduce the problem.
Please change the home attribute in vmInstall element in the plugin.xml before launching the new workspace. The path set in home attribute should be the path of the Java VM which the eclipse is launched with.

You will see two installed JREs with same location. One with "(locked)" and others without "(locked)".
Comment 3 Eiji Morito CLA 2008-09-29 21:59:04 EDT 
Created attachment 113829 [details]
proposed patch

Hi, all.

I attached an proposal patch.
It looks it works fine.
Comment 4 Eclipse Genie CLA 2020-01-23 14:12:11 EST 
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.