Community
Participate
Working Groups
Build: 3.0 M4 I have org.eclipse.pde.core and org.eclipse.pde.ui checked out from CVS. Everything else imported as binary without links. I opened the class org.eclipse.pde.internal.core.ClasspathUtilCore. I selected the static class 'setClasspath'. From context menu, references > Workspace. I got one match. I knew for a fact, there was more than one reference. So I commented out the method and saved. Sure enough, there were five compilation errors. I will attach screen shots. Once upon a time, search used to be solid like a rock. Recently however, I have been experiencing false search results very often.
Created attachment 6502 [details] This is the result returned by Java Search
Created attachment 6503 [details] Problems view These are five compilation errors that resulted from commenting out the method which Java search indicated that it is referenced only once in the workspace.
I followed your steps exactly & I get 5 matches. Can you reproduce this in a new workspace? As for your current workspace, if you delete your index files in the directory .metadata\.plugins\org.eclipse.jdt.core, is it still reproduceable? If not, then somehow in the last while, your index files have become out of date. This would explain the flakeness you've seen lately.
Thanks Kent. Deleting the JDT core metadata solved and reindexing solved the problem.
Can you think of any reason why your index files would have become stale? When did you first start noticing the flakeness?
Not sure. This is actually a relatively new workspace. I created it a day or two before 3.0M4. The flakiness started happening right away. It manifested itself in different forms. another example was the Open type dialog. I would type in the name of a class which I know exists in my workspace; yet the dialog would not find it.
