title: Which IDE settings are OK to checkin?
body: <p>IDEs produce some config files per project/workspace</p>
  
  <p>IntelliJ has it's <code>.idea/</code> folder and it's <code>.iml</code> files.</p>
  
  <p>Eclipse has its <code>.classpath</code> and <code>.project</code> files.
  Eclipse Maven integration used to need a m2e-lifecycle configuration in the pom.xml (not sure if this is still the case)</p>
  
  <p>I've seen projects in the past, </p>
  
  <ul>
  <li>where Eclipse artifacts (.classpath, .project) have been stored in the SVN and it usually broke every developer's workspace. </li>
  <li>where even the m2e-lifecycle configuration was prohibited</li>
  <li>where the m2e-lifecycle configuration was allowed but not .classpath or .project</li>
  <li>where <em>subsets</em> of the <code>.idea/</code> folder is checked in because it contains the run-configurations</li>
  <li>typically .gitignore files contain IDE specific files.</li>
  </ul>
  
  <p>I tend to leave all IDE artifacts out of the sourcecode, including configuration, except the listing of IDE artifacts in the .gitignore.</p>
  
  <p>But I wonder, what are good reasons for / against checking in</p>
  
  <ul>
  <li>IDE generated artifacts (like .classpath or *.iml)</li>
  <li>IDE specific configurations (i.e. in maven poms)</li>
  </ul>
  
  <p>into the SCM?</p>
  
  <p>Or is it a general No-Go?</p>