title: maven dependency managment and version change of transitive dependency
body: <p>How to safely manage with such a problem:</p>
  <p>In maven we have 2 libs (A with version 20, B with version 30) that depends on C (1.0 and 1.1 respectively). We get jar hell in target libs</p>
  <pre><code>*--A20--C1.0
  \--B30--C1.1
  </code></pre>
  <p>Then I add dependencyManagment section and force C version to 1.1. It works as expected.</p>
  <pre><code>*--A20--C1.1 (not C1.0)
  \--B30--C1.1
  </code></pre>
  <p>After several months, we decide to upgrade A to version 50. Now it depends on C version 2.0. But project still uses 1.1 due to dependencyManagement. It's a problem now</p>
  <pre><code>*--A50--C1.1 (not C2.0 as needed)
  \--B30--C1.1
  </code></pre>
  <p>The question is: is it possible to override transitive dependency and this override will work only if version of transitive dependency match the version we set? Otherwise this override will be ignored and we'll see an error (with help of maven-enforcer plugin, for instance) I wonder if we have some plugin to check this case?</p>