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

Eli Smaga commented on MNG-7049:
--------------------------------

[~michael-o] Can you point me to where in the Maven code base the downloading 
of all the pom files is being done, and also what action in the 
DefaultVersionRangeResolver is triggering that to happen? Sorry, but I am 
having hard time figuring that out. Is there a functional reason that Maven 
downloads all of those pom files? I'm asking because I am curious if we disable 
that whether it would cause any downstream issues? Do you know of a way to 
disable that from happening with out having to build a custom version of Maven 
or some other work around?

[~mnk] Did you find a solution or a way to work around 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)

Reply via email to