Why don't you put .classpath files in the repository?
Without these files Eclipse gives very strange errors (you have to add "Plug-in dependencies" library on the classpath).
I've looked at these files and find no developer-specific information, so they can be put in the repository. So what's the reason then?
Maybe the problem is in the JRE? But you can use the workspace default one in that case.
Re: Why don't you put .classpath files in the repository?
You are right. After dropping support for Eclipse 2 we don't have the problem that the .classpath files are wired to a specific version of Eclipse (plugin version number in classpth) anymore.
The only problem left is the full path of the source code locations stored in .classpath files. So if I commit my current .classpath files then Mac OS X paths (e.g. "/Users/torsten/Develop/spring-framework-1.1.5/src) are stored within them :-).
Ok, I will remove the source code locations and commit the .classfiles.