According to the maven documentation / a>, there is the command:
mvn dependency:tree -Dverbose -Dincludes=<biblioteca>
They will specifically return the dependencies that depend on the informed library.
An important detail for this situation is the -Dverbose
attribute, which instructs the dependency tree to display conflicting dependencies. That is, you will have information like omitted for conflict with 2.0
that will help you find the conflicts. However, this attribute is only usable in Maven 2.0, because in version 3.0 of Maven the use of -Dverbose may result in some problems according to documentation :
verbose Whether to include omitted nodes in the serialized dependency
tree. Notice this feature actually uses Maven 2 algorithm and may give
wrong results when used with Maven 3.
That's why when you run the complete command above in Maven 2.0 you might notice the message:
Using Maven 2 dependency tree to get verbose output, which may be inconsistent with current Maven 3 resolution