Summary: | No classpath refresh when replacing binary project with source form | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Philipe Mulet <philippe_mulet> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | john.arthorne, Michael.Valenta |
Version: | 3.0 | ||
Target Milestone: | 3.0 M4 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Philipe Mulet
2003-09-25 12:17:37 EDT
*** Bug 43673 has been marked as a duplicate of this bug. *** *** Bug 43675 has been marked as a duplicate of this bug. *** workaround: close/reopen project Is this possible caused by deltas firing more frequently? We now do periodic POST_CHANGE notifications if sufficient time has elapsed since the last POST_CHANGE. Maybe your delta processor is being fooled by this? Something like that definitely seems to occur. I am also wondering if it is a combination of project deletion/added back with different classpath which gets us into troubles. The delta notification change created a scenario which we did not handle correctly: project description change (no nature change) + classpath change at the same time. We were missing the classpath change. Fixed in latest. Will post a patch. Patch available at: http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-core- home/r3.0/main.html#updates Verified. |