[ https://issues.apache.org/jira/browse/MNG-7049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17407344#comment-17407344 ]
Tuomas Kiviaho commented on MNG-7049: ------------------------------------- {quote}I am so certain that I have seen a similiar request for this, but I can't remember whether it was with Maven Core or Maven Resolver. Will keep looking{quote} [~michael-o] Here's a link to [MRESOLVER-133|https://issues.apache.org/jira/browse/MRESOLVER-133] that you probably were looking for. A CI worker without pre-populated local repository would indeed benefit from this. > Version range resolution downloads all poms, not just the highest version > ------------------------------------------------------------------------- > > Key: MNG-7049 > URL: https://issues.apache.org/jira/browse/MNG-7049 > Project: Maven > Issue Type: Improvement > Components: Core > Reporter: Moti Nisenson-Ken > Priority: Major > > 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: > # Performance - it's downloading numerous poms that aren't needed. > # 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] > -- This message was sent by Atlassian Jira (v8.3.4#803005)