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

Posted to issues@maven.apache.org by "Victor (JIRA)" <ji...@apache.org> on 2016/05/21 16:48:12 UTC

[jira] [Commented] (MSHARED-420) Remove Maven2 specific code

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

Victor commented on MSHARED-420:
--------------------------------

Any reason why some of informations stored in DependencyNode of the tree API is not present in the graph API?

I'm thinking for example about the state... is there some plan to support them again in latest versions?


> Remove Maven2 specific code
> ---------------------------
>
>                 Key: MSHARED-420
>                 URL: https://issues.apache.org/jira/browse/MSHARED-420
>             Project: Maven Shared Components
>          Issue Type: Improvement
>          Components: maven-dependency-tree
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>             Fix For: maven-dependency-tree-3.0
>
>
> All the Apache Maven plugins have had their final Maven-2.2.1 compatible versions released.
> This makes it possible to drop old code in depending projects like this one.
> In this case: remove the {{org.apache.maven.shared.dependency.tree}} package. Plugins should switch to {{org.apache.maven.shared.dependency.graph}} which is more accurate since it uses Aether from the Maven runtime.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)