[MNG-7049] Version range resolution downloads all poms, not just the highest version

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Core
• Assignee: Unassigned
• Reporter: Moti Nisenson-Ken
• Created: 08/Dec/20 13:34
• Updated: 19/Dec/23 11:00

Description

When specifying a version range for a dependency, maven will download and try to resolve all poms in that range which satisfy the range. The usage however is only to use the highestVersion. This causes two issues:

1. Performance - it's downloading numerous poms that aren't needed.
2. Fragility - if the version range covers any "bad" poms, then the build will fail. For example, consider that for a specific version, the parent of a pom is not present in the repository. This is enough to fail any build with a version range covering that specific version, as the range resolution stage will not complete. This is particularly harmful when that version would not be selected as the highest, anyway.

Recommend to have a system property to control the desired behavior - it should be possible to short-circuit loading all the versions and to just to load the highest version.

For another user report of this see: https://stackoverflow.com/questions/25047859/restrict-maven-to-not-download-all-poms

 

Issue Links

• is fixed by: MNG-7960 Artifact collection filtering
• is related to: MRESOLVER-451 Expose version range processing strategies
• is related to: MRESOLVER-133 Improve resolver performance by using breadth-first search