In our enterprise project, we are care about the version change of the
dependency, sometimes our EAR project fail in the production environment
just because of a new version of dependency have be adopted. the version
change just because someone add a new transitive dependency which has the
"shortest path" to the dependency tree root. and in this situation, we
didn't know anything about the final EAR changes.
I am question why maven determine to adopt "nearest definition" to
resolve the dependcy conflicts, can it config it just throw a exception with
enough information, and we can specific write the version of dependency in
the < dependencyManagement > section.
