You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Robert Scholte (Jira)" <ji...@apache.org> on 2021/05/22 15:00:06 UTC

[jira] [Closed] (MSHARED-816) Annotate DependencyNodes with dependency management metadata

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

Robert Scholte closed MSHARED-816.
----------------------------------
    Fix Version/s: maven-dependency-tree-3.1.0
         Assignee: Robert Scholte
       Resolution: Fixed

Fixed in [ae03c028c1ca7857e0992db0825922406af4bec7|https://gitbox.apache.org/repos/asf?p=maven-dependency-tree.git;a=commit;h=ae03c028c1ca7857e0992db0825922406af4bec7]
It is unclear to me why this was uncommented. I've tested it with the Maven Enforcer Plugin and didn't notice any negative effect.

> Annotate DependencyNodes with dependency management metadata
> ------------------------------------------------------------
>
>                 Key: MSHARED-816
>                 URL: https://issues.apache.org/jira/browse/MSHARED-816
>             Project: Maven Shared Components
>          Issue Type: Improvement
>          Components: maven-dependency-tree
>    Affects Versions: maven-dependency-tree-3.0.1
>            Reporter: Richard Atkins
>            Assignee: Robert Scholte
>            Priority: Minor
>             Fix For: maven-dependency-tree-3.1.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Maven31DependencyGraphBuilder has commented out support for collecting the original versions and scopes from resolved DependencyNodes, when the underlying DependencyResolutionResult contains this info. This feature should be re-added, so that consumers like maven-enforcer-plugin can use this metadata in its RequireUpperBoundDeps rule when using maven-dependency-tree 3.x.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)