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

Bug 323582

Summary:	No way to look at EE (description)
Product:	[Eclipse Project] JDT	Reporter:	Dani Megert <daniel_megert>
Component:	Debug	Assignee:	Sarika Sinha <sarika.sinha>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	darin.eclipse, sarika.sinha
Version:	3.6
Target Milestone:	4.21
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Dani Megert

2010-08-25 05:49:21 EDT

3.6 and older.

Currently, there's no way either in the UI or via link to take a look at a specific EE. For example I have no way to see what executable is used when I select e.g. 'JavaSE 1.6' and I have no choice to change/set my custom executable.

Comment 1 Darin Wright

2010-08-30 09:52:48 EDT

The "Execution Environments" prefenence page shows which JRE is bound to each EE. Is this what you are looking for?

Comment 2 Dani Megert

2010-08-30 09:55:20 EDT

(In reply to comment #1)
> The "Execution Environments" prefenence page shows which JRE is bound to each
> EE. Is this what you are looking for?
No, I know that page ;-)

What I'm missing is a away to see the actual EE description.

Comment 3 Eclipse Genie

2019-09-15 04:13:27 EDT

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.

Comment 4 Sarika Sinha

2019-09-15 23:21:50 EDT

@Dani,
EE descriptors are not there after --release option.
So what do you want to see as description for suppose JavaSE-12.
The binaries used will be one which are associated to it.

Comment 5 Eclipse Genie

2021-09-05 17:02:14 EDT

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.

Comment 6 Sarika Sinha

2021-09-06 05:28:36 EDT

Does not seem relevant now.