Coherence between dependency:tree and dependency:list options
-------------------------------------------------------------
Key: MDEP-196
URL: http://jira.codehaus.org/browse/MDEP-196
Project: Maven 2.x Dependency Plugin
Issue Type: Improvement
Components: tree
Affects Versions: 2.0
Reporter: Baptiste MATHUS
Assignee: Brian Fox
Priority: Minor
(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:
bq. 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:
bq. 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.
Cheers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
