Bug 28087

Summary:	on build, findMarkers called 3 times for each project
Product:	[Eclipse Project] JDT	Reporter:	Adam Kiezun <akiezun>
Component:	Core	Assignee:	Kent Johnson <kent_johnson>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	Keywords:	performance
Version:	2.1
Target Milestone:	2.1 M5
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Adam Kiezun

2002-12-11 09:05:45 EST

20021210
1. junit setup
2. do a no-op change to 1 file and save
findMarkers is called 5 times
3 times on the project
and 2 times on the file

this is releted to bug 27764

Comment 1 Kent Johnson

2002-12-11 12:54:52 EST

The 2 calls on the file are separate calls to find JAVA_MODEL_PROBLEM_MARKER & 
TASK_MARKER. Its not possible to ask for multiple marker types so this is as 
good as it gets.

All 3 project calls do not traverse children so they are not problematic, even 
with large projects. They basically access the marker collection, which is 
often empty.

Its not worth it to cache the build path markers given the different locations 
we ask for them. Its only the DEPTH_INFINITE calls on a project which are 
problematic.