title: Maven multi-module: aggregate common dependencies in a single one?
body: <p>I have searched for such a question without finding anything, so here I go.</p>
  
  <p>I have a multi-module maven project. Multiple modules all inherit the same parent, where common dependencies are defined. Among them, there is one my own modules, a 'common' one, where some common functionality is implemented.</p>
  
  <p>My question is: What would be a better practice for common dependencies: Define them all explicitly in the parent, like I currently do? Or define them in a 'common' module, which other modules reference, and then rely on transitivity (like a single-entry-point for common dependencies)?</p>