Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 353721

Summary: Focused package explorer not working if top level element is working set
Product: z_Archived Reporter: Philippe Couton <philippe.couton>
Component: MylynAssignee: Mylyn Inbox <mylyn-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: reckord
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Snapshot with project as top level elements
none
Snapshot with working sets as top level elements none

Description Philippe Couton CLA 2011-08-03 05:31:57 EDT
Build Identifier: I20110613-1736

I use working sets in the package explorer, and set the view presentation to have working sets as top level elements.

However, when I select "Focus on Active Task", the package explorer view becomes empty and always show "Empty task context, unfocus or Alt+click". Switching the top-level element to projects populates the view as expected.

This bug is similar to Bug 334024, but there are some differences in my case:
- the "other projects" root node is NOT displayed,
- I have no CDT related plugin installed,
- No exception in the log.


Reproducible: Always
Comment 1 Philippe Couton CLA 2011-08-09 07:33:13 EDT
Created attachment 201131 [details]
Snapshot with project as top level elements

This snapshot shows Eclipse working as expected using projects as top level elements
Comment 2 Philippe Couton CLA 2011-08-09 07:38:00 EDT
Created attachment 201132 [details]
Snapshot with working sets as top level elements

This snapshot shows that the explorer view is empty when working sets are used as top level elements.

The only change in Eclipse that occurred between the other snapshot and this one is the modification of the top level elements of the explorer view.
Comment 3 Philippe Couton CLA 2011-08-09 07:40:55 EDT
As suggested by Steffen Pingel, I can precises that the context contains only Java file.
Comment 4 Steffen Pingel CLA 2011-08-09 08:59:17 EDT
Thanks for the bug report. I'll try to reproduce this problem. Are all of the projects that contain context elements in the Other working set?
Comment 5 Philippe Couton CLA 2011-08-09 09:06:53 EDT
I have one part dispatched in 5 working sets; the other part falls in the "Other Projects" working sets.

The problem occurs with projects in the "Other Projects" set as well as projects in named working sets.
Comment 6 Steffen Pingel CLA 2012-10-29 14:28:32 EDT
Carsten investigated this further and found the root cause of the problem. This is essentially not related to the CDT bridge but can happen if you have more than one structure bridge installed and the "wrong" bridge ends up handling the filtering. We'll track the fix on bug 334024 which was filed first.

*** This bug has been marked as a duplicate of bug 334024 ***