Bug 230892 - Eclipse Application launch type should provide more details in ILaunchConfiguration
Summary: Eclipse Application launch type should provide more details in ILaunchConfigu...
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: bugday, helpwanted
Depends on:
Blocks:
 
Reported: 2008-05-07 10:06 EDT by Raheel Ashraf CLA
Modified: 2019-09-09 02:28 EDT (History)
1 user (show)

See Also:

Attachments
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 Raheel Ashraf CLA 2008-05-07 10:06:44 EDT 
Build ID:  I20080330-1350

Steps To Reproduce:
I implement a ILaunchesListener2 and in launchesAdded I get a reference to ILaunchConfiguration. However for the Eclipse Application launch type there is no way for me to get additional details out such which plugins is this workspace launched with. Basically I want to be able to find out which of the workspace plugins is this launch going to be based on

More information:
Comment 1 Samantha Chan CLA 2008-05-07 10:27:46 EDT 
This should be opened against PDE.
Comment 2 Chris Aniszczyk CLA 2008-05-07 10:34:27 EDT 
We will investigate in 3.5, we're currently in feature freeze.

The request sounds reasonable.
Comment 3 Curtis Windatt CLA 2009-03-13 14:22:18 EDT 
While this is still a reasonable request, as the attributes stored in an Eclipse launch configuration do not provide useful information, no one has stepped forward to work on it.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:13:15 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.
Comment 5 Julian Honnen CLA 2019-09-09 02:28:38 EDT 
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.