Community
Participate
Working Groups
The launch configuration tabs from org.eclipse.pde.ui all extend from AbstractLaunchConfigurationTab. However, they do not override the #getID method. This prevents clients from inserting tabs into PDE tab groups when a new tab is contributed via the org.eclipse.debug.ui.launchConfigurationTabs extension point.
Darin, what's your thoughts on this since this falls in the land of Debug.
Created attachment 96028 [details] patch I would do something like this.
Thanks!
Created attachment 96077 [details] org.eclipse.pde.ui.patch Thsi would require API changes so we can't do it now due to API freeze. However, here is an improved patch for 3.5
Created attachment 96078 [details] mylyn/context/zip
targetting 3.5
If you just use the strings rather than public constants, then there are technically no API changes (just implementing an inherited method). That way extensions could refer to the tabs. In 3.5, you could migrate to use the public constants. This would enable 3.4 tooling higher up the food chain to contribute extra tabs to the PDE launch configs.
fair enough, I'm OK with that compromise for now
done. Samantha, what are you using PDE's launchers for :)? I'm always curious to see what people are up to.
Created attachment 96084 [details] mylyn/context/zip