Bug 212053

Description Jay Blanton 2007-12-05 14:03:34 EST

I have multiple classes that are displayed in the IDE with errors that do not exist and are not classpath related.  If I take my class that Eclipse is displaying errors for, I can backup the class and create a new class with the same name and same code.  When I do this, the new class does not have any errors until I refresh the workspace and then the errors are displayed again.  If I rename the class file to .txt so that it is not registered as a .class, Eclipse continues to show errors in the .txt file.  One of the classes has access to a Constants class (for instance) in the same package and the Constants class has all public methods and compiles fine.  The referring class does not compile and and keeps giving messages that the Constants class cannot be resolved to the referring class.  It seems to occur once I right click a client application or JUnit and say run as java application or run as JUnit.  Once I do this, the classes appear with errors in them and they cannot be resolved by replacing them from the head in CVS unless I delete them first.

Please let me know if there is any specific information that I can provide.

Thanks,

Jay Blanton