 <p>Have you seen this post recommending the use of section?</p> <p><a href="http://stackoverflow.com/questions/7175398/maven-dependency-resolution-conflicted">Maven dependency resolution (conflicted)</a></p> <p>In short you specify the version you want once in a parent/top-level project and then declare the dependency <strong>without version</strong> in the other projects.</p> <p>EDIT: Does this blog post help? <a href="http://blog.mafr.de/2014/08/30/maven-discovering-dependency-conflicts/" rel="nofollow">http://blog.mafr.de/2014/08/30/maven-discovering-dependency-conflicts/</a></p> <p>It includes a clever command line invocation that lists dependencies in a project via "mvn dependency" and extracts the lines with conflicts.</p> <pre><code>mvn dependency:tree -Dverbose | grep --color=always '(.* conflict\|^' | less -r </code></pre>