Maven Dependency mediation(依赖仲裁原理)

Maven依赖仲裁原理

Dependency mediation - this determines what version of a dependency will be used when multiple versions of an artifact are encountered. Currently, Maven 2.0 only supports using the “nearest definition” which means that it will use the version of the closest dependency to your project in the tree of dependencies. You can always guarantee a version by declaring it explicitly in your project’s POM. Note that if two dependency versions are at the same depth in the dependency tree, until Maven 2.0.8 it was not defined which one would win, but since Maven 2.0.9 it’s the order in the declaration that counts: the first declaration wins.

“nearest definition” means that the version used will be the closest one to your project in the tree of dependencies, eg. if dependencies for A, B, and C are defined as A -> B -> C -> D 2.0 and A -> E -> D 1.0, then D 1.0 will be used when building A because the path from A to D through E is shorter. You could explicitly add a dependency to D 2.0 in A to force the use of D 2.0

根据这个原则，pom应该是使用广度优先搜索的策略，根据从根节点到各个组件节点之间的路径深度来选择。上面的例子可以用下图来表示，最后会选择D1.0的版本。如果想显示的使用D2.0版本，则可以在A中显示的声明D2.0来避免混乱。