You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Jim Hughes (Jira)" <ji...@apache.org> on 2022/02/24 17:07:00 UTC

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

    [ https://issues.apache.org/jira/browse/MNG-7049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497565#comment-17497565 ] 

Jim Hughes commented on MNG-7049:
---------------------------------

[~michael-o] others, I looked at this briefly and tried to write an integration test.  It seems like most IT check only the output of Maven rather than checking on internal work that is done.

Is there something I'm missing that would help write an IT for this behavior?  Otherwise, it may need to be checked in a unit test.

> 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.20.1#820001)