Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319298 - Support EE launch variables
Summary: Support EE launch variables
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.6   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: 3.7 M2   Edit
Assignee: Darin Wright CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-08 14:20 EDT by Andrew Niefer CLA
Modified: 2011-05-26 14:51 EDT (History)
3 users (show)

See Also:

Attachments
patch (16.09 KB, patch)
2010-08-13 16:27 EDT, Darin Wright CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Niefer CLA 2010-07-08 14:20:15 EDT 
It would be nice to be specify something like ${ee_home:J2SE-1.4} in a launch configuration and have that replaced with the JRE home for the corresponding EE according to the installed JRE preferences.
Comment 1 Darin Wright CLA 2010-07-12 09:15:21 EDT 
Which fields/attributes do you want to be able to specify this in?
Comment 2 Andrew Niefer CLA 2010-07-12 11:22:51 EDT 
My initial though was for program arguments and vm arguments. 

 I was setting up an antRunner launch config and wanted to pass -D arguments.
Comment 3 Darin Wright CLA 2010-07-12 11:33:07 EDT 
Moving to JDT debug. Debug provides the UI blocks and resolution of the program/VM arguments.
Comment 4 Darin Wright CLA 2010-08-13 16:27:25 EDT 
Created attachment 176589 [details]
patch

Patch with tests. Also added a selection dialog to choose from existing EE's to configure the variable.
Comment 5 Darin Wright CLA 2010-08-13 16:31:39 EDT 
Applied/Fixed.