Community
Participate
Working Groups
Build ID: I20070921-0919 Steps To Reproduce: 1. Create a new general project with the wizard 2. The 'Project Explorer' view is not updated correctly This error occures, if the creation runs 'fast'. E.g., if you debug the wizard, the view is updated correctly.
This also seems to happen with 3.3.1. See bug 204366 and bug 205231.
Created attachment 79864 [details] Registers contributions using proper priority This addresses the problem of duplicated projects. The root cause is that the source of each contribution for intercepted elements was being remembered using the incorrect prioritization of extensions. This was caused by a regression from the patch for Bug 204428.
Excellent. Thanks, Michael. If you haven't already done so, please release the fix in the development stream for 3.3.2.
Michael, when a project showed up twice, did we have two different objects in the tree, an IProject and an IJavaProject? How did the incorrect prioritization cause this?
Here's what I believe happened: Resource extension added an IProject [verified] Now at this point, the framework identified the set of extensions that could contribute IProject, and the first active extension was marked as the contributor. Because of the mis-prioritization, the resource extension was remembered as the source. Java extension generated a refresh which created an IProject [verified] Because the framework knows who gave it content, it *knows* the Java extension contributed this IProject. The Sorting algorithm identified these two instances as coming from different sources (CommonSorter), and as such sorted then by their user-displayed labels. This meant that they weren't compared for equality of their own means. We might consider addressing this behavior in 3.4 separately. The end result is the viewer thought they were different objects.
*** Bug 205961 has been marked as a duplicate of this bug. ***
is this the same as bug 201784 ?
Michael, we will have an M build towards 3.3.2 tomorrow. The build submission is happening later today. Can you please release this into the maintenance stream? I am not sure what the rules are at this point, but you have my +1 for putting this into 3.3.2.
Please release the fix into HEAD as well, this way it will be used (tested) by a larger group of people.
Released to R3_3_maintenance and HEAD.
Can you explain how severe this bug is ? Would it motivate an emergency delivery (sooner than 3.3.2?). My reading of the steps is that it is not that bad. I tried naively and wasn't able to reproduce...
The issue here occurs with simple projects with the Project Explorer open. I was able to reproduce it without issue. I do think this is a bug worth release since it's very visible and it's a regression.
I agree with Michael - this is very visible and can erode a user's confidence in the IDE, which is very bad. Philippe, if you were trying in a Java perspective you wouldn't see it. Try in the Resource perspective.
I agree with Michael and Steve.
Yes, this is the same issue as bug 201784. We are using bug 201784 to track that the same fix is going into the 3.3.1.1 build.
*** Bug 208337 has been marked as a duplicate of this bug. ***
*** Bug 208462 has been marked as a duplicate of this bug. ***
Verified in M20080205-1130
