Uploaded image for project: 'Maven Dependency Plugin'
  1. Maven Dependency Plugin
  2. MDEP-662

Re-Add Dependency Tree Verbose



    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 3.1.1
    • Fix Version/s: None
    • Component/s: tree
    • Labels:


      Please re-add "mvn dependency:tree -Dverbose".

      Ticket Bounty: 300USD (will send via PayPal to address of authors choice upon feature re-addition with proper Maven 3 support)

      I find the command to be really useful and use it daily to check for transitive dependency clashes.

      It seems the command was removed in maven-dependency-plugin:2.11 because it used an outdated version of the dependency resolution mechanism?

      As a workaround I currently invoke the command like this:
      mvn org.apache.maven.plugins:maven-dependency-plugin:2.10:tree -Dverbose

      It's so useful I even added some colorization in bash:


      function mdt() {
          mvn org.apache.maven.plugins:maven-dependency-plugin:2.10:tree -Dverbose $@ \
              | GREP_COLOR='01;31' grep --color=always -E 'omitted for conflict with|$' \
              | GREP_COLOR='01;31' grep --color=always -E 'version managed from|$' \
              | GREP_COLOR='01;32' grep --color=always -E 'omitted for duplicate|$' \
              | GREP_COLOR='01;35' grep --color=always -E ':test|$'

      I execute this command every time I wonder if I messed up any transitive dependencies. It's a really good and quick sanity check command, and I think there's a strong user case for it.

      Sadly the workaround I use is an incorrect one. It will lie. The proper solution is probably to readd the feature with the new Aether resolution mechanism (Maven 3)?

      Examples of other people asking for the same thing:

       Related Maven Link:



          Issue Links



              • Assignee:
                rfscholte Robert Scholte
                Olof Larsson Olof Larsson
              • Votes:
                0 Vote for this issue
                5 Start watching this issue


                • Created: