You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kn Unk (JIRA)" <ji...@codehaus.org> on 2012/03/14 21:16:02 UTC

[jira] (MNG-5262) improve mvn dependency:tree - add optional xml output of the results

Kn Unk created MNG-5262:
---------------------------

             Summary: improve mvn dependency:tree - add optional xml output of the results
                 Key: MNG-5262
                 URL: https://jira.codehaus.org/browse/MNG-5262
             Project: Maven 2 & 3
          Issue Type: Improvement
          Components: Command Line
    Affects Versions: 3.0.4
         Environment: all
            Reporter: Kn Unk


The output of mvn dependency:tree would be more useful to me if it was in a format that is machine readable.  I would like to create some tooling to be able to easily determine what is causing a particular jar to be included.

for example:

>mymvntool -why org.springframework:org.springframework.beans:3.0.5
org.springframework.beans-3.0.5 is being *dragged* in by: my.otherproject.core:1.1
%end of search

another use:

>mymvntool -makeexclusionfor org.springframework:org.springframework.beans:3.0.5
<exclusions>
 <exclusion>
   <groupId>org.springframework</groupId>
   <artifactId>org.springframework.beans</artifactId>
 <exclusion>
</exclusions>

or even:

>mymvntool -makeexclusionfor org.springframework:*:3.0.5

this would pickup all the included jars in the project and build exclusions for them. 
It may have been dumb to pick spring as the exclusion resource, but this is just an example.  having xml output would be valuable to me and probably others too.

-K


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira