jira-importer opened a new issue, #105: URL: https://github.com/apache/maven-dependency-tree/issues/105
**[Elias Lundell](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=JIRAUSER307139)** opened **[MSHARED-1454](https://issues.apache.org/jira/browse/MSHARED-1454?redirect=false)** and commented In maven-dependency-plugin there are multiple export formats for the dependency tree, these include Json, DOT, GraphML etc. When creating the normal tree all information is there to format it nicely as e.g. Json. However, when running ``{}mvn dependency:tree -Dverbose{`}`, all nodes are included (as they are VerboseDependencyNode) but since VerboseDependencyNode is internal in maven-dependency-tree there is no (clean) way to include information of which nodes are included or not (see https://issues.apache.org/jira/browse/MDEP-962). The only current way to include this information would be to parse the ``{}toNodeString(){`}` output (where excluded nodes are wrapped in parenthesis). I propose to expose ConflictData on the DependencyNode and make it null for DefaultDependencyNode to allow for more detailed information in the machine-readable formats. --- **Remote Links:** - [GitHub Pull Request #50 ](https://github.com/apache/maven-dependency-tree/pull/50) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
