Bug 170941 - Be able to specify a Execution Environment when launching a Eclipse Application
Summary: Be able to specify a Execution Environment when launching a Eclipse Application
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: 3.4 M2   Edit
Assignee: Adam Archer CLA
QA Contact:
URL:
Whiteboard:
Keywords: contributed
Depends on:
Blocks:
 
Reported: 2007-01-18 11:40 EST by Willian Mitsuda CLA
Modified: 2007-09-12 04:24 EDT (History)
4 users (show)

See Also:
baumanbr: review+


Attachments
patch (18.54 KB, patch)
2007-08-29 14:07 EDT, Adam Archer CLA
no flags Details | Diff
patch (18.53 KB, patch)
2007-09-05 11:47 EDT, Adam Archer CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Willian Mitsuda CLA 2007-01-18 11:40:04 EST
Currently, it is possible only to specify a JRE on "Eclipse Application" launcher. The "Java Application" launcher has this capability.

A possible solution would be to remove the "Java Runtime Environment" section from the "Main" tab and reuse the "JRE" launch tab from JDT.
Comment 1 Chris Aniszczyk CLA 2007-08-27 22:55:04 EDT
Hey Adam, guess what, more stuff to do :D

Tagging this bugday also with the hope that Janek might come out of nowhere and attempt something :)

Let's target to 3.4
Comment 2 Adam Archer CLA 2007-08-29 14:07:35 EDT
Created attachment 77279 [details]
patch

I opted not to reuse the Java launcher section since we have other things in our JRE area. Plus, keeping things in the same place will ensure that we do not disorient people. Also, less tabs means less clutter.
Comment 3 Adam Archer CLA 2007-09-05 11:47:08 EDT
Created attachment 77737 [details]
patch

Previous patch got out of sync. This is the same thing synced again against head.
Comment 4 Brian Bauman CLA 2007-09-07 17:06:13 EDT
I like it.  Works very well.  I would have thought the JDT guys created it ;-)  Thanks Adam!

Also included a minor tweak to the Listener.  Since we attached a listener to all radio buttons, when the selection changes we get two events.  The Listener now discards the deselection event, thereby only updating the launch configuration once when a radio selection changes (instead of twice).