[
https://issues.apache.org/jira/browse/MNG-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249399#comment-15249399
]
Michael Hüttermann commented on MNG-5997:
-----------------------------------------
Hi [~rfscholte],
thanks for the hint. After introducing a pretty big batch of entries for
dependencyManagement, accordingly, the first daily use of the goal provokes
even more roundtrips to local Maven repository manager to fetch even more and
other *maven-metadata.xml* files than before. Does this "work as designed"?
> 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
>
> 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)
