[jira] [Updated] (MDEP-435) improve mvn dependency:tree - add optional xml output of the results

["Michael Osipov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MDEP-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated MDEP-435:
--------------------------------
    Labels: close-pending  (was: )

> improve mvn dependency:tree - add optional xml output of the results
> --------------------------------------------------------------------
>
>                 Key: MDEP-435
>                 URL: https://issues.apache.org/jira/browse/MDEP-435
>             Project: Maven Dependency Plugin
>          Issue Type: Improvement
>          Components: tree
>         Environment: all
>            Reporter: Kow Unk
>              Labels: close-pending
>
> 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 was sent by Atlassian JIRA
(v6.3.15#6346)