(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:
- both should support a very simple -Dincludes/-Dexcludes option that would just do a simple kind of grep inside the groupId/artifact (even version ?)
- 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.
- is duplicated by
MDEP-502 Add parameter "includes" to dependency:list