Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
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.
Attachments
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
- Closed
-
MENFORCER-427 Rule for no version ranges, version placeholders or SNAPSHOT versions
- Closed
- links to