Summary: | Indexer: Double-Indexing on Specific Project | ||
---|---|---|---|
Product: | [Tools] CDT | Reporter: | Mathieu Lapensée <lapensee> |
Component: | cdt-core | Assignee: | Bogdan Gheorghe <gheorghe> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | major | ||
Priority: | P3 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0.1 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Mathieu Lapensée
2004-09-07 16:33:47 EDT
I'll have a look... It is possible that this is happening when you 1. Create a project 2. Indexer runs in background 3. Do a build (which will cause the paths and symbols to update) 4. The path and symbol update will "dirty" the state of all files 5. Indexer will run on all the "dirty" files. Ok. I redid the test with workflow: 1) Create a Standard project 2) In properties, turn off indexer 3) Put the source in (import the file system or copy file over in explorer and refresh project in eclipse) 4) Build project 5) Turn on Indexer. Unfortunately, it indexes twice the whole project (1700+ files). This is using our product with CDT 200408271356. 6) After the indexing is finished, do another build as another test to make sure that the indexer is not triggered again. After executing it, the indexer was not triggered. 7) Close the project. 8) Open the project. The indexer get triggered and does it Just to finish step 8. It indexed the project once. After investigation, it looks like there are 2 culprits at work here: i) Importing a standard project, with Auto Build on, which triggers a build, which kicks off the scanner discovery, which adds new include paths, which kicks off a new index ii) A-OK bug: hitting Apply once you enable the indexer schedules a new indexing job, so does hitting OK. So if you hit both of them, then you get 2 indexes... - BG Fixed - hitting apply or OK will trigger only one indexing job. - BG |