Bug 98969 - Builder didn't find state for prereq project
Summary: Builder didn't find state for prereq project
Status: CLOSED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 RC2   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-08 11:10 EDT by Jerome Lanneluc CLA
Modified: 2005-06-10 11:46 EDT (History)
0 users

See Also:

Attachments
Builder trace (160.37 KB, text/plain)
2005-06-08 11:11 EDT, Jerome Lanneluc CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jerome Lanneluc CLA 2005-06-08 11:10:30 EDT 
N20050608 + JDT Core HEAD

1. My development workspace was started with a pure N20050608
2. I exited and patched JDT Core (contained the fix for bug 98906)
3. I restarted my development workspace and build
4. Full builds started as expected, but failed after a while (see attached
builder trace) as the build state for org.eclipse.test.performance was not found.
However I verified that there was a state.dat file in
.metadata\.plugins\org.eclipse.core.resources\.projects\org.eclipse.test.performance\org.eclipse.jdt.core
Comment 1 Jerome Lanneluc CLA 2005-06-08 11:11:08 EDT 
Created attachment 22612 [details]
Builder trace
Comment 2 Jerome Lanneluc CLA 2005-06-08 11:19:16 EDT 
Note that when I exited my workspace, it was fully built.
Comment 3 Kent Johnson CLA 2005-06-08 11:32:46 EDT 
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.
Comment 4 Philipe Mulet CLA 2005-06-08 17:06:47 EDT 
+1 for RC2
Comment 5 Jerome Lanneluc CLA 2005-06-08 17:18:27 EDT 
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.
Comment 6 Olivier Thomann CLA 2005-06-09 09:55:10 EDT 
Once I patch jdt/core, it doesn't look like a full build was done.
Comment 7 Olivier Thomann CLA 2005-06-09 10:36:18 EDT 
Verified in  N20050609-0010 + JDT/Core HEAD.
The full build occured and completed fine.
Comment 8 Frederic Fusier CLA 2005-06-10 11:46:12 EDT 
Verified for 3.1 RC2 using build I20050610-0010