Konrad Windszus opened MNG-7561 and commented
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
|
if ( versionConstraint.getRange() == null ) |
when the range has the same upper and lower bound.
Issue Links:
-
MNG-7106 VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds
-
MENFORCER-427 Rule for no version ranges, version placeholders or SNAPSHOT versions
Remote Links:
Backported to: 4.0.0-alpha-3, 3.9.0, 3.8.9
0 votes, 5 watchers
Konrad Windszus opened MNG-7561 and commented
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
maven/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultVersionRangeResolver.java
Line 108 in 3f90e70
Issue Links:
MNG-7106 VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds
MENFORCER-427 Rule for no version ranges, version placeholders or SNAPSHOT versions
Remote Links:
Backported to: 4.0.0-alpha-3, 3.9.0, 3.8.9
0 votes, 5 watchers