Community
Participate
Working Groups
We should consider adding an extension point so that a plugin could contribute a number of prefilled external tool configurations so the user does not need to create these manually.
To be considered for post 2.0 (original suggestion from Kevin H)
Could a product install do this by modifying some file internal to external tools?
We store the tool configurations in an XML file. Someone could modify this file to add extra tools. However, we do not publish what the format of that file is.
*** Bug 21806 has been marked as a duplicate of this bug. ***
Reopening to investigate for 2.1.
*** Bug 21907 has been marked as a duplicate of this bug. ***
Since we are now using launch configs, there should actually be debug platform support for defining a "pre-filled" launch configuration. Moving to debug as a feature request.
Not committed for 2.1
Is there still an interest for this feature (CC list)?
Talk with Kevin H.
Kevin, is there still an interest for this feature?
Was this enhancement request ever implemented or was there insufficient interest?
Never implemented. Does not seem overly popular.
Closing. It feels like other tooling could accomplish this without an extension point. For example, a plug-in could create a launch config via API the first time it starts up, or a common launch config could be supplied via a shared file in a repository. Please open a new bug with more explicit requirements if something else is required.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.