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

["Konrad Windszus (Jira)" <ji...@apache.org>]

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

Konrad Windszus edited comment on MNG-8205 at 8/10/24 9:55 AM:
---------------------------------------------------------------

Anything speaks against deprecating in Maven 4 already and point to Maven 4 API (instead of Resolver API)? Otherwise consumers won't know which one is the correct way in Maven 4...

Maven 4 API is still marked as experimental though...


was (Author: kwin):
Anything speaks against deprecating in Maven 4 already and point to Maven 4 API (instead of Resolver API)? Otherwise consumers won't know which one is the correct way in Maven 4...

> 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- Maven 4 API (https://github.com/apache/maven/tree/master/api/maven-api-core/src/main/java/org/apache/maven/api) directly.



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