title: What is the Maven way for automatic project versions when doing continuous delivery?
body: <p>I have a web application where we deploy to production whenever a feature is ready, sometimes that can be a couple of times a day, sometimes it can be a couple of weeks between releases. </p>
  
  <p>Currently, we don't increment our version numbers for our project, and everything has been sitting at version <code>0.0.1-SNAPSHOT</code> for well over a year.
  I am wondering what is the Maven way for doing continuous delivery for a web apps. It seems overkill to bump up the version number on every commit, and never bumping the version number like we are doing now, also seems wrong.</p>
  
  <p><strong>What is the recommend best practice for this type of Maven usage?</strong></p>
  
  <p>The problem is actually a two-fold one:</p>
  
  <ul>
  <li>Advancing project version number in individual <code>pom.xml</code> file (and there can be many).</li>
  <li>Updating version number in all dependent components to use latest ones of each other.</li>
  </ul>