You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/12/09 19:00:00 UTC

[jira] [Commented] (MSHARED-1454) Conflict Data on VerboseDependencyNode is hidden

    [ https://issues.apache.org/jira/browse/MSHARED-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17904255#comment-17904255 ] 

ASF GitHub Bot commented on MSHARED-1454:
-----------------------------------------

LogFlames commented on PR #50:
URL: https://github.com/apache/maven-dependency-tree/pull/50#issuecomment-2529114858

   Would this be a feasible change to enable verbose logging output in maven-dependency-plugin? If it is preferable I could create a PR to maven-dependency-plugin that is dependent on this one to have all code-changes in context.
   
   @elharo wdyt?




> 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
>            Priority: Minor
>              Labels: pull-request-available
>
> 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)