Summary: | Builder didn't find state for prereq project | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jerome Lanneluc <jerome_lanneluc> | ||||
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> | ||||
Status: | CLOSED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | ||||||
Version: | 3.1 | ||||||
Target Milestone: | 3.1 RC2 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Jerome Lanneluc
2005-06-08 11:10:30 EDT
Created attachment 22612 [details]
Builder trace
Note that when I exited my workspace, it was fully built. Jerome, how did you trigger the build? I think we need to make sure that ALL projects are touched when we detect a changed external jar file... otherwise in cases when the build state version number has changed, its possible that a prereq project will not be built & its build state will be useless. I've added to the debug info to identify when a prereq build state's version # is out of date. +1 for RC2 Changed JavaCore#initializeAfterLoad() to check if the build state version number is different from the previous session. If this is the case, touch every single Java project in the workspace to ensure that they all will be rebuilt. Once I patch jdt/core, it doesn't look like a full build was done. Verified in N20050609-0010 + JDT/Core HEAD. The full build occured and completed fine. Verified for 3.1 RC2 using build I20050610-0010 |