maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] [Updated] (MNG-5997) Continuous download of maven-metadata.xml for version ranges.
Date Wed, 20 Apr 2016 07:42:25 GMT


Robert Scholte updated MNG-5997:

I've attached a small project based on

You only have to put pom files in {{src/it/mrm/repository}} and adjust the pom of {{src/it/projects/project1}}.
Start adding dependencies, etc and run {{mvn clean verify}} until the project fails because
it starts downloading a metadata file.
The theory is that it should only download metadata files in case of version ranges (and SNAPSHOT
is a special kind of range)

> Continuous download of maven-metadata.xml for version ranges.
> -------------------------------------------------------------
>                 Key: MNG-5997
>                 URL:
>             Project: Maven
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 3.2.2
>            Reporter: Michael Hüttermann
>            Priority: Critical
>         Attachments:
> 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

View raw message