Xiang Li created MRESOLVER-164:
----------------------------------
Summary: DefaultDependencyCollector filterVersions seems always
return full version range
Key: MRESOLVER-164
URL: https://issues.apache.org/jira/browse/MRESOLVER-164
Project: Maven Resolver
Issue Type: Bug
Affects Versions: 1.6.1, 1.4.2
Reporter: Xiang Li
Related to MNG-7049 but I think the root cause is in maven-resolver so I opened
a new issue. Correct me if it is better to still use the old ticket.
During using version ranges, I notice that maven will download all poms from a
version range, which happen in that
[loop|https://github.com/apache/maven-resolver/blob/master/maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/collect/DefaultDependencyCollector.java#L404],
the reason is that
[verFilter|https://github.com/apache/maven-resolver/blob/master/maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/collect/DefaultDependencyCollector.java#L155]
here seems return null. Since by default, versionFilter is set to null by
DefaultRepositorySystemSession, and I do not see many examples that
setVersionFilter get used for some reason.
Another thing that confuses me is that version range is resolved by
DefaultVersionRangeResolver in maven rather than maven-resolver here.
I wonder if it possible to set HighestVersionFilter
[here|https://github.com/apache/maven-resolver/blob/master/maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/collect/DefaultDependencyCollector.java#L155]
instead of return all version range results.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
