> I work on a lot of projects and having eclipse (or any other IDEs) project files in the SCM is > almost ever causing a problem. In praxis those files are always dirty. There are so many settings > which may be different from user to user true. however, those problems can easily be avoided by the policy of not ever checking in those eclipse files unless coordinated within the project. we have many big java projects here internally and _do_ have the eclipse settings in git. it makes life so much easier for everyone to start work and we have many more settings in there that we actually want enforced. for example: we enforce a coding standard through eclipse by automatically formatting the source code and organising imports on file save. also, we want everybody to use the same settings when cleaning up the code. we want them to use the same findbugs settings, the same settings for xxx/yyy/.... > * different JVM settings if specified correctly this is actually an advantage: you can standardise your projects on a (minimum) JVM platform, like 1.5 > * using different version of various plugins we see that as an advantage so that we can standardise the development setup, or at least define some sort of minimum setup > You can easily create the project files for a few IDEs with maven e.g.: > $> mvn eclipse:eclipse for creating the eclipse project files > $> mvn idea:idea for creating the idea project files I know, quite handy :-) Think I have more questions now than before by discussing it :-) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html