Bug 226952 - [CommonNavigator] Refreshing issues in Project explorer with self updating working sets
Summary: [CommonNavigator] Refreshing issues in Project explorer with self updating wo...
Status: RESOLVED DUPLICATE of bug 212389
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Francis Upton IV CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2008-04-14 11:35 EDT by Neeraj Agrawal CLA
Modified: 2009-01-15 11:02 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Neeraj Agrawal CLA 2008-04-14 11:35:16 EDT 
Build ID: 3.4

Steps To Reproduce:
I have :

1. Working sets types implementing IWorkingSetUpdater.

2. Using IWorkingSet.setElements(IAdaptable[]) to update the working set with the new projects created in the workspace meeting a specific rule.


In the project explorer Top Level Elements are selected as working sets. 

When the new projects are created in the workspace, they are being added to the Working sets as mentioned in step 2, but they are displayed in the Project explorer view.  If you select "Select Working Set" dialog, and navigate to the specific working set, the project is selected.


More information:
Comment 1 Eric Moffatt CLA 2008-04-14 16:06:21 EDT 
Neeraj, do you get the same result using the Package Explorer rather than the Project Explorer? I'm trying to figure out if it's a working sets issue or if it's specific to the view...
Comment 2 Neeraj Agrawal CLA 2008-04-14 16:12:09 EDT 
Works great with package explorer
Comment 3 Francis Upton IV CLA 2008-08-20 00:39:52 EDT 
Can you try this with M20080820-0800 (3.4.1), or any nightly after N20080819 (3.5)?  There were a few fixes in this area that might have resolved this problem.
Comment 4 Francis Upton IV CLA 2008-08-25 17:36:08 EDT 
This is likely fixed by bug 212389.
Comment 5 Francis Upton IV CLA 2009-01-15 05:22:03 EST 
Please reopen if this is a problem in either 3.4.1 or 3.5M3 or higher.
Comment 6 Francis Upton IV CLA 2009-01-15 11:02:32 EST 

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