maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thorsten Jacoby (JIRA)" <>
Subject [jira] [Updated] (MNG-6156) Resolving dependencies is not thread-safe
Date Wed, 24 May 2017 15:16:04 GMT


Thorsten Jacoby updated MNG-6156:

Vielen Dank für Ihre Email.

Ich bin am 29.05.2017 wieder im Haus.

Ihre Email wird nicht weitergeleitet.

Mit freundlichen Grüßen
Thorsten Jacoby

> Resolving dependencies is not thread-safe
> -----------------------------------------
>                 Key: MNG-6156
>                 URL:
>             Project: Maven
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 3.3.9
>            Reporter: Roland Illig
>         Attachments: dependency-list.txt,,
> When building a multi-module project in parallel, Maven updates the local Maven repository
without taking into account that other threads or processes might do the same at the same
> To reproduce:
> 1.  unpack the attached project
> 2.  {{mvn dependency:list -U -B -T100}}
> See the attached {{dependency-list.txt}} for an example output.
> First thing to notice is that the dependency is downloaded 100 times. This is unexpected,
since the Reactor should coordinate all the modules.
> Second thing to notice is that the build fails, since a dependency "cannot be found".
This is wrong, since the dependency _can_ be found, it's just not processed properly.
> I suspect the {{legacy.DefaultWagonManager}} to be the cause of this, since the typical
error messages are:
> * {{"Downloaded file does not exist: "}}
> * {{"Error copying temporary file to the final destination: "}}

This message was sent by Atlassian JIRA

View raw message