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 2023/06/01 19:10:00 UTC

[jira] [Commented] (MNG-7548) Kill off "legacy" repository metadata support

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

ASF GitHub Bot commented on MNG-7548:
-------------------------------------

gnodet opened a new pull request, #1138:
URL: https://github.com/apache/maven/pull/1138

   JIRA issue: https://issues.apache.org/jira/projects/MNG/issues/MNG-7548
   
   




> Kill off "legacy" repository metadata support
> ---------------------------------------------
>
>                 Key: MNG-7548
>                 URL: https://issues.apache.org/jira/browse/MNG-7548
>             Project: Maven
>          Issue Type: Improvement
>          Components: Artifacts and Repositories
>            Reporter: Tamas Cservenak
>            Assignee: Guillaume Nodet
>            Priority: Major
>
> Maven 3.0 introduced repository metadata model version "1.1.0" (MNG-4452), while Maven 2 used repository metadata model version "1.0.0" (could not resolve snapshot artifacts having classifiers).
> Current Maven should never generate "legacy" metadata anymore, as 2.x line is EOL, and model version is in effect since Maven 3.0.
> Mixing metadata causes issues like MRESOLVER-224 (alas, this is actually MINVOKER issue, as it "crafts" legacy metadata using pure DOM)



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