| Summary: | Focused package explorer not working if top level element is working set | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Philippe Couton <philippe.couton> | ||||||
| Component: | Mylyn | Assignee: | 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
Philippe Couton
Created attachment 201131 [details]
Snapshot with project as top level elements
This snapshot shows Eclipse working as expected using projects as top level elements
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.
As suggested by Steffen Pingel, I can precises that the context contains only Java file. 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? 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. 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 *** |