Description Chris West (Faux) 2010-03-19 02:47:35 EDT

Build Identifier: I20100312-1448

Described is the testcase.  This actually happens more frequently than just directly after start in the source project (http://git.goeswhere.com/?p=catchlogger.git , with Expression and Op being the affected classes), but far less reproducibly.  I hope it's the same bug.

Attached project contains two files:
Alice.java: class Alice { Object j = Bob.CHARLIE; }
Misc.java: enum Bob { CHARLIE; }

If only Alice.java is open when Eclipse is starting up, the editor thinks that "Bob cannot be resolved to a variable".  This is /not/ reported in the Problems view.

Go to definition / any other completion etc. does not work on Bob inside Alice.java.

Starting Eclipse with Misc.java open, however, makes this problem Go Away; Alice.java presents fine in the editor and Bob's completion etc. works fine.

Sometimes saving Alice.java / Misc.java make the problem go away, too; not entirely sure on the combinations.

(I'm wildly guessing that the indexer indexes the open files before the others, and reindexes in an unpredictable order)

The attached screenshot shows only Alice.java open in an editor directly after Eclipse has started.  Brand new workspace / project.

Reproducible: Always

Steps to Reproduce:
Thorough steps:
1. Start Eclipse with a clean workspace.
2. Import -> Existing projects into workspace.
3. Give it the directory containing the extracted attached sample project.
4. Open Alice.java (and /only/ Alice.java) in an editor (you may see the problem here).
5. Restart Eclipse with this workspace.
6. Alice.java should be open, and Bob should be redunderlined in the current view.