Community
Participate
Working Groups
F3/Win32 We have a plugin which can switch our projects between binary and source much like the PDE. Binary mode points the src to nowhere but the build libraries point to the JARs and source does the reverse. When we convert between binary and source, we notice that the Java Perspective loses the Project in the UI. If I go to the Resources view, the Project still exists. I must close then open the project to make the Java Perspective show the project again. Seems like a notification is being lost or ignored but I don't really know where to look. I thought it was the JavaModelCache, but that wasn't it.
We'd need more detailed information to track this down. You could have a look at PackagExplorerContentProvider.processDelta to see how the Package Explorer deals with deltas. That might give you an idea of what delta you miss to send out or which delta we forget to process.
So what I see is that when you get the CHANGED event, the project is missing. What I don't understand is how this gets built. Basically the CHANGED event has all the projects except the one we are processing. Looking at the code its similar to the pde PluginImportOperation. I will change our code to follow exactly what you do to see if there is something screwy that has changed since M5 to cause this.
Ok, here is some more info... During this processing, you are being told that the Project is deleted. Then the DeltaProcessor is being told that the Project is being replaced and has a description (0xc0000 or 0x80000). However the Java Model that is created as part of traverseDelta does not contain the package. I am not clear how this code works but its tossed somewhere in there.
JDT Core has fixed some problems related to Java projects not being updated properly. Moving to JDT Core for comment.
This really sounds like bug 19799, which is fixed in latest build. Could you please try build 20020620 and let us know if this fixes the problem?
Closing, please reopen if symptoms are still occurring on latest build (20020620). *** This bug has been marked as a duplicate of 19799 ***
