Summary: | Fail to build on workspace restart after upgrade | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jerome Lanneluc <jerome_lanneluc> | ||||||
Component: | Core | Assignee: | Kent Johnson <kent_johnson> | ||||||
Status: | RESOLVED WORKSFORME | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P3 | CC: | philippe_mulet | ||||||
Version: | 3.1 | ||||||||
Target Milestone: | 3.2 M6 | ||||||||
Hardware: | PC | ||||||||
OS: | Windows XP | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Jerome Lanneluc
2005-05-25 05:33:37 EDT
Created attachment 21703 [details]
Builder trace since the begining of the session
No luck reproducing the trace... I suspect the missing build state files may explain why jdt.core was not built at all. Access rule changes to core.runtime are causing full builds in the 'upgrade tests' I tried, but each project was able to find its build state & rebuilt successfully. These are the options I'm running with: # Turn on debug tracing for org.eclipse.jdt.core plugin org.eclipse.jdt.core/debug=true # Reports incremental builder activity : nature of build, built state reading, indictment process org.eclipse.jdt.core/debug/builder=true # Turn on debugging for the org.eclipse.core.resources plugin. org.eclipse.core.resources/debug=true # Reports the start and end of all builder invocations org.eclipse.core.resources/build/invoking=true Created attachment 21799 [details]
Builder trace for N20050526
After I upgraded from N20050525 to N20050526, I got a full build (as expected)
but this time jdt.core was correctly built (and dependent projects as well).
However not that the previous build state was still not found, and the trace
still doesn't show were the build state is supposed to be.
Also this looks very suspicious: Starting build of org.eclipse.jdt.core @ Thu May 26 10:30:10 CEST 2005 About to read state... Successfully read state for org.eclipse.text <--- !!!!!!!!! Performing full build since last saved state was not found FULL build It might be a race condition between the external jar refresh that is done in a separate job on start up, and the builder. Changed DeltaProcessor#checkExternalArchiveChanges(...) to touch all the affected projects at once (by taking the workspace lock). Also the build state is reset at the same time, but this should be removed when we have support for external jars timestamps in the build state. Please reopen if the problem persists with the latest builds reopening to close, since never reproduced in a long time closing |