title: Synchronizing Eclipse .classpath in code repository
body: <p>My team handles several Java projects using Eclipse, and shares the code using a code repository.</p>
  
  <p>When a developer adds, removes or updates a <code>jar</code> file, the build is broken for everybody else, until they update their build path in Eclipse. This process involves cumbersome email synchronization.</p>
  
  <p>For several reasons, we have decided not to commit the <code>.classpath</code> file to the repo. Instead, we came up with the following idea: Each project will have a committed file, say <code>jars.list</code>, which contains a list of <code>jar</code> files (and patterns). A script will convert this file into a local <code>.classpath</code> for eclipse. Whenever a developer changes its jars, it is his or her responsibility to change <code>jars.list</code> and commit it.</p>
  
  <p>Is this a reasonable solution? Are there any existing solutions for this problem?</p>