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

Coherence between dependency:tree and dependency:list include/exclude options

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.0
    • Fix Version/s: None
    • Component/s: tree
    • Labels:

      Description

      (The "list" component seems to be missing. That's why I only selected the "tree" one).

      I think dependency:tree and dependency:list should at least try to share the same filtering options. For example, I just ran this on my project:

      mvn dependency:tree -Dincludes=org.springframework

      Then I wanted to see the resulting list after the transitive dependency resolution, so I just replaced tree by list:

      mvn dependency:list -Dincludes=org.springframework

      But indeed this won't work, since for dependency:list you have to put -DincludeGroupIds instead of -Dincludes.

      What it should do in my opinion:

      1. both should support a very simple -Dincludes/-Dexcludes option that would just do a simple kind of grep inside the groupId/artifact (even version ?)
      2. both should then also support -DincludeGroupIds/includeArtifactIds as specific options.

      This would improve the global usability and coherence of the plugin. Also note that other mojos of the dependency-plugin could be improved by this unification (resolve*, sources, unpack...).

      Thanks a lot.
      Cheers.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                mathus.b@mipih.fr Baptiste MATHUS
              • Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: