| Summary: | [Navigator] Duplicate projects in Navigator | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Michael Valenta <Michael.Valenta> |
| Component: | UI | Assignee: | Kim Horne <eclipse> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jean-michel_lemieux, n.a.edgar |
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Michael Valenta
What may be happening here is that opening the Navigator fetched the projects from the workspace root which returned the ones that were already loaded. The resource delta that was fired when the checkout was complete added all projects to the Navigator. This process does not check whether the projects already exist. Bug 40214 is related. Reassigning to Nick since he is taking ownership of the Navigator. The next integration build will contain incremental change event notification which will make this more obvious than it previously was. Another note, duplicate entries in the navigator are not limited to projects. I've seen folders duplicated as well. Tod, could you please put in an exists check for now? Added in exists check for 20030923 Kim There is a workaround for this currently in TreeViewer add() so you will likely have to remove it to replicate this. The incremental updates work without the exist() check, however as we discussed, it seems sensible that the same object cannot be added to a given parent node more than once. The exists() check should remain to take care of this. |