[
https://issues.apache.org/jira/browse/MNG-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17614704#comment-17614704
]
Konrad Windszus commented on MNG-7529:
--------------------------------------
In fact the filtering of remote repos is already done in
https://github.com/apache/maven-resolver/blob/master/maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/DefaultMetadataResolver.java#L413,
so my previous statement is incorrect. Not sure about version ranges
containing both releases and SNAPSHOTs (MNG-3092) so I am actually not sure if
{{Metadata.Nature}} needs to be changed in
https://github.com/apache/maven/blob/ce4579108d653be2ab7eab43be7d5951151dae5b/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultVersionRangeResolver.java#L151.
> 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: Tamas Cservenak
> 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)
