title: Maven - Multiple artifact versions in dependency management
body: <p>Is there a valid use case for having two different versions of the same artifact in the dependency management section of your POM?</p>
  
  <p>I'm looking at a project whose root POM contains such an example. The project itself has multiple modules using different versions of this "duplicate dependency". Some of the modules thus have to specify the artifact's version explicitly among their dependencies so as to distinguish between the two.</p>
  
  <p>If the POM files of the modules have to specify the version anyway, what is the reason for having the duplication in the parent's dependency management? The dependency would get looked up properly even if it was removed from dependency management, so why would you duplicate it there in the first place?</p>
  
  <p>I'm just trying to figure out if this is good practice or if there's a better solution to such a situation.</p>