You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2022/11/27 10:40:00 UTC
[jira] [Updated] (MNG-7561) DefaultVersionRangeResolver should not try to resolve versions with same upper and lower bound
[ https://issues.apache.org/jira/browse/MNG-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated MNG-7561:
---------------------------------
Summary: DefaultVersionRangeResolver should not try to resolve versions with same upper and lower bound (was: DefaultVersionRangeResolver should not try to resolve request with same upper and lower bound)
> DefaultVersionRangeResolver should not try to resolve versions with same upper and lower bound
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-7561
> URL: https://issues.apache.org/jira/browse/MNG-7561
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: 3.9.0, 4.0.0, 4.0.0-alpha-3
>
>
> For dependencies having e.g. version {{[1.0]}} the DefaultVersionRangeResolver still tries to resolve versions although only a single version (namely 1.0) is valid here according to https://maven.apache.org/pom.html#Dependency_Version_Requirement_Specification.
> This leads in the worst case to long-running calls against a remote repository for no reason.
> There should be a shortcut in https://github.com/apache/maven/blob/3f90e7028e0338c110aea267b44362653d55273a/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultVersionRangeResolver.java#L108 when the range has the same upper and lower bound.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)