title: How to release Maven multi-module project with inter-project dependencies?
body: <p>Lets say we have 3 layers project. DB, Business, Web and aggregating pom.  </p>
  
  <pre><code>Project  
  |-DB  
  | |-pom.xml  
  |-Business  
  | |-pom.xml  
  |-pom.xml
  </code></pre>
  
  <p>All modules are ment to be released and branched together, so Aggregator pom is configured to assign the same version to all submodules. We have the following versions:  </p>
  
  <pre><code>DB-0.1-SNAPSHOT  
  Business-0.1-SNAPSHOT which depends on DB-0.1-SNAPSHOT  
  Web-0.1-SNAPSHOT which depends on Business-0.1-SNAPSHOT  
  </code></pre>
  
  <p>When doing <code>release:prepare</code>, all versions updated to 0.1, but prepare fails because there is no <code>DB-0.1</code> in dependency yet.</p>
  
  <p>One solution is to create different projects for every module and release them one by one while using <code>versions:use-releases</code> plugin to update dependency to 0.1</p>
  
  <p>But I do not like this idea because it requires a lot of configuration and scripting. So, I prefer to use aggregation and release all modules with single command, but the problem is, as I wrote above, when release plugin tries to build <code>Business-0.1</code> there is no <code>DB-0.1</code> in repository yet.</p>
  
  <p>Is there any way to manage these inter-project dependencies?</p>
  
  <p>Thanks.</p>
  
  <p>UPD:  </p>
  
  <p>even install goal fails.  </p>
  
  <ol>
  <li>DB Build - OK (no snapshot nor release version is in any repository)  </li>
  <li>Business - Failure (DB-0.1-SNAPSHOT not found in repository. But it's even not supposed to be there yet!)  </li>
  </ol>
  
  <p>I'm using maven 3.0.2 and release plugin 2.1  </p>