Community
Participate
Working Groups
Build ID: I20080617-2000 Steps To Reproduce: Hello, This is an enhancement request. When I want to import whole bunch of plugins from a framework this is what I do: 1) Fire plugin import wizard. 2) Enter a meaningful something to filter 3) Add all 4) (!) Hunt down the source plugins and remove from list of selected plugins to import I think importing a source plugin makes no sense. I therefore, think that, PDE Plugin import wizard should be optionally) smarter not list the source plugins at all. Regards, Hasan Ceylan More information:
There is some interest in being able to import a source plugin and have it be treated as a source location in the workspace. See bug 232841. That being said, the case is unusual. Cleaning up source bundles in the UI is planned for 3.5, but how it is done depends on what changes are made to the target platform.
Thanks for the prompt info.
I would even categorize this as a regression. Before the advent of source bundles (when source was bundled in one source plug-in per feature), this has not been an issue.
Created attachment 117944 [details] Proposed Fix In the long term we will want to consider a more complete solution to handling source bundles (bug 249065). In the mean time this fix will allow users to filter the import wizard using a check box (source plugins will be filtered by default).
Created attachment 117945 [details] mylyn/context/zip
This fix depends on a change to PDEState that keeps auxilliary data (specifically the source bundle header around). See bug 242002.
Fixed in HEAD.
