Community
Participate
Working Groups
In 3.3M6 (and I'm pretty sure in past versions), the product ID has no bearing as to what is calculated by the 'Add Required Plug-ins' button. 1. Open the 'Run' dialog. 2. Create a new 'Eclipse Application' launch configuration. 3. Select 'org.eclipse.sdk.ide' for the 'Run a product:' drop down combo control. 4. Go to the 'Plug-ins' tab. 5. Select 'plug-ins selected below only' in the 'Launch with:' drop down combo control at the top. 6. Deselect 'Workspace' and 'Target Platform', setting the configuration as '0 out of XXX selected'. 7. Hit the holy and sacred be all end all 'Add Required Plug-ins' button. 8. And...nothing happens.
Created attachment 63820 [details] Patch for illustrative purposes. This patch won't always work since I noticed that org.eclipse.ui.ide.application 's application ID is actually org.eclipse.ui.ide.workbench, so my string concatenation check will fail. Maybe the method I am using is incorrect? Can someone from the PDE team comment on this?
will try to look into 3.3, setting temp target milestone now
*** Bug 98999 has been marked as a duplicate of this bug. ***
For 3.3, we could use the simplistic approach that the first n-1 segments of a product/application ID indicate the contributing plug-in ID. After bug 166610 is done, it would be pretty simple to map from a product ID to its plug-in.
Created attachment 68461 [details] patch When inintializing the PluginBlock, we retain a reference to the launch configuration. When computing the 'Add Required', we query the launch configuration to get the product/application ids. We simplistic n-1 approach from comment #4 to find the plug-in it is from. If the plug-in exists, we check to see if it checked. If it is not, we then check it. After we do this, we call super's function to add the required plug-ins.
Mike, when you get a chance can you be the second reviewer on this patch if Chris hasn't already reviewed it. He has been really busy with other work so I am not sure if he will have time.
Good patch. Thanks Brian.
Comment on attachment 68461 [details] patch Patch tested well Brian.
Patch released to HEAD.
Looks good to me on RC2, thank you PDE team! :)