title: Jenkins maven build dependent projects?
body: <p>I have a project with multiple modules say "Application A" and "Application B" modules (these are separate module with its own pom file but are not related to each other).</p>
  
  <p>In the dev cycle, each of these modules have its own feature branch. Say,</p>
  
  <pre><code> Application A --- Master
                    \
                     - Feature 1
  
   Application B --- Master
                    \
                     - Feature 1
  </code></pre>
  
  <p>Say Application A is independent and has its own release cycle/version.</p>
  
  <p>Application B uses Application A as a jar. And is defined in its pom dependency.</p>
  
  <p>Now, both teams are working on a feature branch say "Feature 1". What is the best way to setup Jenkins build such that, Build job for Application B is able to use the latest jar from "Feature 1" branch of Application A. </p>
  
  <p>Given Feature 1 is not allowed to deploy its artifacts to maven repository.</p>
  
  <p>Somehow I want the jar from Application A's Feature 1 branch to be supplied as the correct dependency for Application B?</p>