[MNG-7561] DefaultVersionRangeResolver should not try to resolve versions with same upper and lower bound

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.8.9, 3.9.0, 4.0.0-alpha-3, 4.0.0
• Component/s: Artifacts and Repositories
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 12/Oct/22 07:07
• Updated: 07/Apr/23 15:17
• Resolved: 07/Nov/22 16:04

Description

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.

Issue Links

• is related to: MNG-7106 VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds
• is related to: MENFORCER-427 Rule for no version ranges, version placeholders or SNAPSHOT versions
• links to: GitHub Pull Request #823
• links to: GitHub Pull Request #864