Bugzilla – Full Text Bug Listing
| Summary: | Support EE launch variables | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Andrew Niefer <aniefer> | ||||
| Component: | Debug | Assignee: | Darin Wright <darin.eclipse> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | ankur_sharma, darin.eclipse, Michael_Rennie | ||||
| Version: | 3.6 | ||||||
| Target Milestone: | 3.7 M2 | ||||||
| Hardware: | PC | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Which fields/attributes do you want to be able to specify this in? My initial though was for program arguments and vm arguments. I was setting up an antRunner launch config and wanted to pass -D arguments. Moving to JDT debug. Debug provides the UI blocks and resolution of the program/VM arguments. Created attachment 176589 [details]
patch
Patch with tests. Also added a selection dialog to choose from existing EE's to configure the variable.
Applied/Fixed. |
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.