[MRESOLVER-164] DefaultDependencyCollector filterVersions seems always return full version range

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.2, 1.6.1
• Fix Version/s: 2.0.0-alpha-5, 2.0.0
• Component/s: Resolver
• Assignee: Unassigned
• Reporter: Xiang Li
• Created: 18/Feb/21 23:36
• Updated: 14/Jan/24 21:03
• Resolved: 14/Jan/24 21:03

Description

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, the reason is that verFilter 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 instead of return all version range results. I am happy to contribute a PR with some guidance.

Issue Links

• is fixed by: MNG-7960 Artifact collection filtering