Summary: | Projects not build in correct order after load (1GF60TN) | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | DJ Houghton <dj.houghton> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0 M1 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Bug Depends on: | 3435 | ||
Bug Blocks: |
Description
DJ Houghton
2001-10-10 22:52:58 EDT
This is a direct consequence from the fact that a VCM load is only perceived as a resource change, and the JavaModel cannot change project references when reconciling with the new .classpath file. Project references cannot be updated: * when noticing the .classpath change because it is too soon (still inside change notification) * when building, because it is too late So we leave them as is. Only the JavaUI updates them when doing the classpath change in the UI. This is not acceptable, but given the current design of the platform, I do not see how we could solve this one. PRODUCT VERSION: 0.122 JRE on Win98 |