[jira] [Commented] (MNG-8205) Deprecate o.a.m.artifact

["Tamas Cservenak (Jira)" <ji...@apache.org>]

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

Tamas Cservenak commented on MNG-8205:
--------------------------------------

Some context:
* in "maven 3 universe" they DO duplicate and introduce alternate semantics for Artifacts and more importantly Versions (basically we have two parallel implementations of artifacts and versions)
* in "maven 4 universe" API introduces third implementation, but goal is to hide the existing two from plugins, essentially Maven 4 API is replacing both with one.
* the resolver as standalone library will still keep artifact/version implementations, while Maven Core ones should be dropped somewhere in the future, when Maven4 API becomes the one and only possible thing to reach from Maven4 plugins and extensions.

> Deprecate o.a.m.artifact
> ------------------------
>
>                 Key: MNG-8205
>                 URL: https://issues.apache.org/jira/browse/MNG-8205
>             Project: Maven
>          Issue Type: Improvement
>          Components: Artifacts and Repositories
>            Reporter: Konrad Windszus
>            Priority: Major
>
> The classes within {{org.apache.maven.artifact}} (https://github.com/apache/maven/tree/master/maven-artifact/src/main/java/org/apache/maven/artifact) mostly duplicate code from Maven Resolver API (https://github.com/apache/maven-resolver/tree/master/maven-resolver-api/src/main/java/org/eclipse/aether). Therefore they should be deprecated and consumers should use the Resolver API directly.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)