Increment version in every Jenkin's build and update dependencies
<p>I have a number of Maven projects being built my Jenkins server. These projects have dependencies on each other, e.g. </p>

<pre><code>service-base -&gt; java-base -&gt; pom-base
</code></pre>

<p>In other words, the Maven project <code>service-base</code> depends on the Maven project <code>java-base</code>. Naturally, my POM files look like this:</p>

<pre class="lang-xml prettyprint-override"><code>&lt;project&gt;
  &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
  &lt;groupId&gt;my.com&lt;/groupId&gt;
  &lt;artifactId&gt;service-base&lt;/artifactId&gt;
  &lt;dependencies&gt;
    &lt;dependency&gt;
        &lt;groupId&gt;my.com&lt;/groupId&gt;
        &lt;artifactId&gt;java-base&lt;/artifactId&gt;
        &lt;version&gt;1.0.0&lt;/version&gt;
    &lt;/dependency&gt;
  &lt;/dependencies&gt;
&lt;/project&gt;
</code></pre>

<p>The issue is that none of my Maven projects have "releases" per-se, since I'm using continuous integration to release my changes. Currently, I allow artifact overwriting in my Maven repo and keep all of my versions at <code>1.0.0</code>. This is because I release my packages many times a day and changing the versions in all the POM files each time I submit a new package version.</p>

<p>Ideally, what I would like is for Jenkins to generate a new version, e.g. <code>1.0.{BUILD_NUMBER}</code> and then for it update the dependencies all the way up the dependency tree.</p>

<p><strong>Question</strong>: Is this possible? Or does anyone have any other solutions to versioning? </p>