You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/22 13:37:00 UTC

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

     [ https://issues.apache.org/jira/browse/MNG-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliotte Rusty Harold closed MNG-5997.
--------------------------------------

> 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
(v8.3.4#803005)