Bug 15177 - Classpath markers not correctly updated
Summary: Classpath markers not correctly updated
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 M6   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-03 07:25 EDT by Philipe Mulet CLA
Modified: 2002-05-03 10:40 EDT (History)
0 users

See Also:

Attachments
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 Philipe Mulet CLA 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 CLA 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.