Summary: | Java Projects disappear | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Michael Fraenkel <fraenkel> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | P4 | CC: | jerome_lanneluc |
Version: | 2.0 | ||
Target Milestone: | 2.0 F4 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Michael Fraenkel
2002-06-19 09:41:38 EDT
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? |