Bug 210591 - Allow External Tools to use Default JRE
Summary: Allow External Tools to use Default JRE
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-21 16:16 EST by Martin H. CLA
Modified: 2019-09-06 16:08 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin H. CLA 2007-11-21 16:16:16 EST
In the External Tools JRE tab, there is no way to select the default JRE.  It's best to explain with an example...

I'm running Eclipse on a 1.6 JRE and according to ant -diagnostics, the "run with workspace JRE" option gives me this JRE.

My default JRE is named JDK_1.4 and that's what I compile with.  But, the .classpath files, do not refer to it my name, it refers to it using "JRE_CONTAINER"  this allows me to modify the default without having to update all my projects.

With External tools, I have to explicitly select JDK_1.4 and the .launch file will reference JDK_1.4 so I'm not able to fully hide the actual value of the default JRE.

Could you please add a new option on the External Tools JRE tab for "Workspace Default JRE"... Actually, you probably need another option for "Project Default JRE" I don't use it but I know that you can override the JRE at the project level.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:08:00 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.