[
https://issues.apache.org/jira/browse/MNG-7548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728687#comment-17728687
]
ASF GitHub Bot commented on MNG-7548:
-------------------------------------
gnodet commented on PR #1138:
URL: https://github.com/apache/maven/pull/1138#issuecomment-1573534252
> LGTM, but as issue mentions, we have other places to look into as well
@cstamas What are you referring it ? I read the issue again but I don't
see...
> 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)
