[jira] [Commented] (MNG-7529) Maven resolver makes bad repository choices when resolving version ranges

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

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

Konrad Windszus commented on MNG-7529:
--------------------------------------

This fix is IMHO incorrectly filtering the results afterwards while it needs to prevent asking SNAPSHOT remote repositories for metadata.xml in the first place when resolving non-SNAPSHOT versions. Why can't we just set the correct nature in https://github.com/apache/maven/blob/ce4579108d653be2ab7eab43be7d5951151dae5b/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultVersionRangeResolver.java#L151 in the first place?

> Maven resolver makes bad repository choices when resolving version ranges
> -------------------------------------------------------------------------
>
>                 Key: MNG-7529
>                 URL: https://issues.apache.org/jira/browse/MNG-7529
>             Project: Maven
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 3.8.6
>            Reporter: Henning Schmiedehausen
>            Assignee: Tamás Cservenák
>            Priority: Major
>             Fix For: 3.8.x-candidate, 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> This is the same problem as MRESOLVER-270. The problem is actually in the maven core, not in the resolver. See the description there.
>  
> This bug is a placeholder for the fix PR.



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