Community
Participate
Working Groups
in bug 72678 there was talk of having things like "add RCP plugins" and such to places where users are specifying lists of plugins. This would of course be useful but is very specific. People developing pluings in other scenarios will have different base sets of plugins that need to be manipulated. I am hereby floating the idea (half baked as it is) of some notion of bundle groups in PDE. Think of them as working sets are to JDT etc. People can define them, name them, add them, remove them etc. An obvious helper would be to have features surfaced as immutable bundle groups. Using this mechanism we can define some canonical groups (e.g., Base RCP) and users can have the option of adding these to their targets or launch configurations...
What's the difference between a 'bundle group' and a 'feature'?
as with IBundleGroup, features are surfaced as bundle groups but bundle groups need not be features. It would be WAY to heavy weight to say that if I want to group together a few plugins in my dev environment I should create a feature or even to have that happen under the covers.
In more familiar Eclipse terms, what is needed here is a PDE "working set". This would be a pretty good idea.
Done. There is now a "Plug-ins" working set. Places where you can directly access it and use it are: 1. The target platform preference page. 2. The plugins tab of the launch configuration. 3. The plug-in export wizard.
Part of this effort, I also added an "Add Required Plug-ins" button to the target platform preference page as per one of Jeff's early requests.
