[ https://jira.codehaus.org/browse/MDEP-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte moved MNG-5262 to MDEP-435: ------------------------------------------ Complexity: (was: Intermediate) Component/s: (was: Command Line) tree Affects Version/s: (was: 3.0.4) Key: MDEP-435 (was: MNG-5262) Project: Maven Dependency Plugin (was: Maven 2 & 3) > improve mvn dependency:tree - add optional xml output of the results > -------------------------------------------------------------------- > > Key: MDEP-435 > URL: https://jira.codehaus.org/browse/MDEP-435 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: tree > Environment: all > Reporter: Kow 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 For more information on JIRA, see: http://www.atlassian.com/software/jira