Community
Participate
Working Groups
Created attachment 112784 [details] Image showing the problem Build ID: 3.4 Steps To Reproduce: 1) Create a "Plug-in and Fragments Working Set" selecting some plugins (either in the workspace or provided by the platform). 2) Select the working set in the Project Explorer view. 3) The projects don't have icons, and their labels state: "Error: no label provider for org.eclipse.pde.internal.ui.util.PersistablePluginObject@..." This seems to happen every time. More information: Screenshot attached.
*** This bug has been marked as a duplicate of bug 212389 ***
Still happens in HEAD (I20090707-0800) if the "Plug-in and Fragments" working set contains an external plug-in (from the target platform).
Created attachment 141738 [details] Plugins&Fragments working set with Team Provider Damaged label provider.
(In reply to comment #2) > Still happens in HEAD (I20090707-0800) if the "Plug-in and Fragments" working > set contains an external plug-in (from the target platform). > This happens also for "normal" plugin/fragment projects which are connected with a team provider. See my attachment.
(In reply to comment #4) > (In reply to comment #2) > > Still happens in HEAD (I20090707-0800) if the "Plug-in and Fragments" working > > set contains an external plug-in (from the target platform). > > > > This happens also for "normal" plugin/fragment projects which are connected > with a team provider. See my attachment. > This happend in version 3.5.
No plans to fix. I don't know why plug-in and fragment working sets even exist.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.