title: spring-boot-starter-jetty and Jetty modules - Maven magic
body: <p>We're using spring-boot-starter-jetty in our maven pom, which means we don't have any direct dependency on jetty hence no control on its version.</p>
  
  <p>This all works good, but we now need to add a dependency onone of jetty's modules, which are using the same jetty version convention.</p>
  
  <p>This is all great and dandy, but because we can't use spring-boot-starter-jetty as our root pom, we're declaring jetty's version again under the module's dependency declaration, something like this:</p>
  
  <pre><code>&lt;dependency&gt;
     &lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
     &lt;artifactId&gt;spring-boot-starter-jetty&lt;/artifactId&gt;
     &lt;version&gt;1.4.3-RELEASE&lt;/version&gt;
  &lt;/dependency&gt;
  &lt;dependency&gt;
     &lt;groupId&gt;org.eclipse.jetty&lt;/groupId&gt;
     &lt;artifactId&gt;jetty-nosql&lt;/artifactId&gt;
     &lt;version&gt;9.3.14.v20161028&lt;/version&gt;
  &lt;/dependency&gt;
  </code></pre>
  
  <p>This is no fun PLUS dangerous as if we upgrade one of them, we have to remember to upgrade the latter to the same version.</p>
  
  <p>I know we can add an exclude under the module's dependency but this feels like a hack plus still doesn't fully protect us from breaking changes.</p>
  
  <p>Is there anyway to extract the jetty version from spring boot and reuse it for the module's dependency?</p>
  
  <p>Thanks!!</p>