Bug 5203 - Project indexing does not restrain to source files on the classpath
Summary: Project indexing does not restrain to source files on the classpath
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P2 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-24 09:00 EDT by Philipe Mulet CLA
Modified: 2002-01-11 09:22 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 Philipe Mulet CLA 2001-10-24 09:00:05 EDT 
A user on EC reported that when indexing his project containing 2.000 files,
we ended up processing 40.000 files.

His setup has a lot of symbolic links to denote the same files over and over, 
but none of these are actually located on the classpath (but the original
2000 files).

The code for indexing the project visits the entire project, and does not 
restrain itself to package fragment roots. Therefore it ends up processing
the entire set of .java files in the project.
Comment 1 Jerome Lanneluc CLA 2001-10-24 10:22:34 EDT 
See ProjectResourceCopier to see how to traverse the resource tree.
Comment 2 Jerome Lanneluc CLA 2001-10-31 07:35:56 EST 
Fixed IndexAllProject to visit only source folders (and not the entire project 
as it used to do).

Also fixed DeltaProcessor to not update the index for .java files that are 
outside the classpath.