Bug 15177

Summary:	Classpath markers not correctly updated
Product:	[Eclipse Project] JDT	Reporter:	Philipe Mulet <philippe_mulet>
Component:	Core	Assignee:	Philipe Mulet <philippe_mulet>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	2.0
Target Milestone:	2.0 M6
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Philipe Mulet

2002-05-03 07:25:30 EDT

Build 20020502

In an empty workspace, auto-build off, import all prerequisite projects
for org.eclipse.jdt.core as library projects.

At the end of the import process, the xerces project is tagged with an error 
indicating boot is missing though it is present.

Comment 1 Jerome Lanneluc

2002-05-03 10:40:46 EDT

Problem is that projects are added and setRawClasspath(...) is called in one 
workspace runnable:

When xerces is added, boot is not yet present. Then a setRawClasspath(...) is 
done which generates a problem marker. Then boot is added. At the end of the 
workspace runnable, the delta processor refreshes the markers of boot's 
dependents only, not the marker of boot.

Fixed to refresh the markers of the added projects as well.