Elias Lundell created MSHARED-1454:
--------------------------------------
Summary: Conflict Data on VerboseDependencyNode is hidden
Key: MSHARED-1454
URL: https://issues.apache.org/jira/browse/MSHARED-1454
Project: Maven Shared Components
Issue Type: New Feature
Components: maven-dependency-tree
Reporter: Elias Lundell
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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
