[jira] [Comment Edited] (MNG-5997) Continuous download of maven-metadata.xml for version ranges.

["Michael Hüttermann (JIRA)" <ji...@apache.org>]

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

Michael Hüttermann edited comment on MNG-5997 at 5/31/16 6:58 AM:
------------------------------------------------------------------

Thanks. Due to some basic conditions, I cannot add a dependencyManagement section to the underlying POM now. I call the Maven goal {{com.this:com.that:go}} from the command line (the executed Maven plugin has those dependencies defined as version ranges in its POM(s)). I've tried now to add the called plugin {{com.this:com.that}}, in the used version, to the "build" section of my POM and added "dependency" elements in its dependencies plugin section to nail down the exact versions to use. Unfortunately, again, all dependencies are checked again for updates and roundtrips to the binary repo occur. :-( Any idea how to get rid of these roundtrips? 
Thank you.


was (Author: michaelhuettermann):
Thanks. I call the Maven goal {{com.this:com.that:go}} from the command line, and the executed Maven plugin has these dependencies defined as version ranges in its POM(s). What's the recommended way to cope with that scenario and to apply your tips? Maybe to add the called 3rd party plugin to the "build" section of my POM and adding "dependency" elements in that plugin section to nail down the exact versions to use? Thank you.

> Continuous download of maven-metadata.xml for version ranges.
> -------------------------------------------------------------
>
>                 Key: MNG-5997
>                 URL: https://issues.apache.org/jira/browse/MNG-5997
>             Project: Maven
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 3.2.2
>            Reporter: Michael Hüttermann
>            Priority: Critical
>         Attachments: MNG-5997.zip
>
>
> With every first build of the day, Maven downloads *maven-metadata.xml* from remote repository. Generally, this is ok since the default update policy enforces an update. But: the daily synced dependency artifacts are release artifacts, in the declaration form of:
> {code}
> <dependency>
>     <groupId>com.this</groupId>
>     <artifactId>com.that</artifactId>
>     <version>[1.0.0,1.0.1)</version>
>     <type>jar</type>
> </dependency>
> {code}
> So looks like the daily roundtrips are performed since there are version ranges defined?! Since there are hundreds of dependencies, this takes a pretty long time, and nothing did change, operationally, because I've already downloaded all required dependencies.
> Please suppress these daily roundtrips of downloading  *maven-metadata.xml*, for that use case, in general a check for new updates should be applied of cause (thus just using the offline mode is not a solution).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)