Bug 28087 - on build, findMarkers called 3 times for each project
Summary: on build, findMarkers called 3 times for each project
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.1 M5   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2002-12-11 09:05 EST by Adam Kiezun CLA
Modified: 2002-12-11 12:54 EST (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 Adam Kiezun CLA 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 CLA 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.