Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 312710 - [target] Target editor loses track of missing plug-ins when both features and plug-ins are included
Summary: [target] Target editor loses track of missing plug-ins when both features and...
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on: 312085
Blocks:
  Show dependency tree
 
Reported: 2010-05-12 16:35 EDT by Curtis Windatt CLA
Modified: 2019-06-28 12:53 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Curtis Windatt CLA 2010-05-12 16:35:20 EDT
1) Create a target definition pointing at an Eclipse install
2) On content tab, change to manage by features
3) Deselect everything except one feature and one plug-in from the "other plug-ins' section
4) Switch to location tab, edit the location
5) Change the location to be another directory containing at least one plug-in, but does not the one feature and one plug-in selected in (3).
Result:
The editor says you are missing one required feature, there is no mention of the missing plug-in.  The actual file still has the correct includes, unless you save the target definition at which point it is overwritten.

This is caused by a change in TargetDefinition.filterBundles() line 450.  We call getMatchingBundles, but only pass in a parent status if there are no feature includes.  This was done to prevent getting a huge list of missing plug-in errors when a feature was missing.
Comment 1 Curtis Windatt CLA 2010-05-20 11:33:00 EDT
Moving to 3.7.  Could consider for 3.6.1 if there is a well contained fix.
Comment 2 Eclipse Genie CLA 2019-06-28 12:53:58 EDT
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.

--
The automated Eclipse Genie.