Eclipse project corruption

[James Daniel]

I am using Eclipse Galileo. I have it installed on a couple computers and the issue is occuring on both. Every so often a lot of my classes will show errors and imports will show as invalid. I have to delete the project and then check it out from Subversion. Overwriting from Subversion does not fix it. I has to be deleted and then re-checked out. I know it isn't a code issue since it is the same exact code that is in Subverion. It is getting seriously annoying. If anyone has seen this and has an answer, please pass it along.

[Peter Johnson]

Details, please! How can we help you fix errors if you don't tell us what the errors are?

[David Newton]

I rarely have to do anything other than clean the project and rebuild--but I haven't actually had this problem frequently, if at all, since 3.3.

[Amir Iqbal]

Dear James,
yeah same things happens to me too. But i realized is, there is some sort of bug in eclipse. How i solve it is, you can check your project's libs and you will realize that The JRE path is changed. That's why there are so many issues highlighted in code. Just reset the JDK/JRE path then you will find its fixed. ok.



Regards,
Amir Iqbal

[Tim Holloway]

I get this problem when I'm doing an external compile (maven) that fails. Eclipse gets totally confused even after I fix the problem and compile clean.

I don't have a totally cookbook solution, but stopping and restarting Eclipse is a start along with a Refresh operation. Usually that doesn't fix a whole lot, however, since apparently there's some scrambled project metadata. Often "touching" a module will make it recover. I suppose a manual Eclipse "rebuild" might help, but I haven't tried.

[James Daniel]

Thanks for all for the suggestions. I was just wondering if I was just me. At least I feel a little better knowing I'm not the only one. Hopefully newer versions will resolve this issue.

[James Daniel]

David,

Although the clean doesn't prevent the issue from occurring, it does fix it so I don't have to delete then re-checkout the whole project from Subversion and start over. Thanks so much for the tip.

I guess my rage was blinding me. = )

Jim