title: Dealing with Maven snapshots - best practices
body: <p>I'm no maven guru by a long shot but I would appreciate some help.</p>
  
  <p>Here's the situation:</p>
  
  <p>I work in a large, distributed development team using Maven 2. We have a Nexus repository but it only holds releases, not snapshots.</p>
  
  <p>The problem is 2-fold:</p>
  
  <ol>
  <li><p>Every morning I have to svn up other modules I do not work on, build them and then build my module. This is because my module has snapshot dependencies on these other modules. This takes time and really adds up as everyone needs to do this to stay current.</p></li>
  <li><p>Say module A needs module B and is declared as a snapshot dependency. Module B is updated to a higher version number but the developer forgets to update module A pom. So module A is using an older snaphot and it may not be identified for a while, probably only when its time to do a release.</p></li>
  </ol>
  
  <p>So how best to deal with these issues?</p>