[MDEP-196] Coherence between dependency:tree and dependency:list include/exclude options

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.0
• Component/s: tree
• Labels: S2
• Assignee: Unassigned
• Reporter: Baptiste MATHUS
• Created: 15/Jan/09 08:08
• Updated: 23/Oct/23 06:41

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.

Issue Links

• is duplicated by: MDEP-502 Add parameter "includes" to dependency:list