title: Maven Multi Module benefits over simple dependency
body: <p>I have some years of experience with maven projects, even with multi modules ones (which has made me <em>hate</em> the multi modules feature of maven (so the disclaimer is now done)) and even if I really like maven there is something I cannot get a clear answer about : </p>
  
  <p><strong>What is a typical usecase of a multi module maven project ? What is the added value of such a structure compared to simple dependencies and parent pom ?</strong></p>
  
  <p>I have seen a lot of configuration of multi module projects but all of them could have clearly been addressed by creating a simple structure of dependency library living their own life as deliverables (even with a parent pom, as a separate deliverable : factorising depedencies and configuration) and I haven't found any usecase where I can clearly see an added value of the multi module structure. </p>
  
  <p>I have always found that this kind of structure brings an overkilling complexity with no real benefit : where am I missing something ? (to be truly honest, I can get that some <code>ear</code> can benefit from this kind of structure but except from that particular usecase, any other real use and benefit ?)</p>