title: maven parent pom with different child versions
body: <p>There are multiple modules in our applications and each of them have their separate version and depend on other modules(external to our organization). They all have a parent POM which has it's own version, independent from the children's version.</p>
  
  <p>When one of those modules change, they're converted to snapshots.</p>
  
  <p>For the following example:</p>
  
  <pre><code>Parent v14.0
  - module1 v1.5.0
      - dependency1(module2 v15.0.0)
      - dependency2(external-jar v12.0.1)
  - module2 v15.0.0
  - module3 v3.1.0
  </code></pre>
  
  <p>If there would be a change in module2, then module2's version would become v15.0-SNAPSHOT, then module1 becomes v1.5-SNAPSHOT. The parent remains the same.
  The purpose for not having the same version on parent+modules, is that we want to localize the updates made to some modules and not affect the others' versions.</p>
  
  <p>This has been designed like this a long time ago and there are several bash scripts to support the updates, although they're not handling all the cases. In any case, we don't have a one-click release process and we feel we are quite far from it with this approach.</p>
  
  <p>We don't know how to convince the management towards a single version approach on all modules. How do you feel about the above? Did you ever encountered a project using the above structure and how well did it go?</p>
  
  <p>Thank you!</p>