score:62

Accepted answer

two more general-purpose mechanisms for fixing some of eclipse's idiosyncrasies:

  • close and open the project
  • delete the project (but not from disk!) and reimport it as an existing project

failing that, bugs.eclipse.org might provide the answer.

if the workspace is caching something broken, you may be able to delete it by poking around in workspace/.metadata/.plugins. most of that stuff is fairly transient (though backup and watch for deleted preferences).

score:2

just

  • close project
  • clear manually output folder(s)
  • open project

(eclipse 3.5 sr2, build id: 20100218-1602)

score:3

closing the projects didn't do the trick for me. i started eclipse with the -clean flag and that worked for some reason.

score:5

i also encountered this issue recently, the below scenario worked for me.

  1. close eclipse
  2. delete <workspace>/.metadata/.plugins/org.eclipse.jdt.core/*.index
  3. delete <workspace>/.metadata/.plugins/org.eclipse.jdt.core/savedindexnames.txt
  4. start eclipse again

score:7

got this error to the other day. tried deleting the all .class-files and resources from my output folder manually. didn't work. restarted my computer (winxp). didn't work. closed my project in eclipse and opened it again. worked!!! hopes this solves someones problem out there. the search facilities and truly essential to eclipse.

score:72

comment #9 to bug 269820 explains how to delete the search index, which appears to be the solution to a corrupt index whose symptoms are the dreaded

an internal error occurred during: "items filtering".
class file name must end with .class

message box.

how to delete the search index:

  1. close eclipse
  2. delete <workspace>/.metadata/.plugins/org.eclipse.jdt.core/*.index
  3. delete <workspace>/.metadata/.plugins/org.eclipse.jdt.core/savedindexnames.txt
  4. start eclipse again

Related Query

More Query from same tag