maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roland Illig (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6156) Resolving dependencies is not thread-safe
Date Mon, 16 Jan 2017 12:10:26 GMT

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

Roland Illig commented on MNG-6156:
-----------------------------------

Thanks for the reply. Your instructions were a bit vague, so here is what I tried:

* {{svn checkout http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-dependency-plugin}}
* {{(cd maven-dependency-plugin && mvn install)}}
* {{(cd MNG-6156 && mvn org.apache.maven.plugins:maven-dependency-plugin:3.0.1-SNAPSHOT:list
-T100 -U -B}} (reliably fails)
* {{(cd MNG-6156 && mvn org.apache.maven.plugins:maven-dependency-plugin:3.0.0:list
-T100 -U -B}} (reliably fails)

Of which command do you want the _log file with debug logging enabled_? What kind of debugging
log, just {{-X}}?



> Resolving dependencies is not thread-safe
> -----------------------------------------
>
>                 Key: MNG-6156
>                 URL: https://issues.apache.org/jira/browse/MNG-6156
>             Project: Maven
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 3.3.9
>            Reporter: Roland Illig
>         Attachments: dependency-list.txt, wagon-not-threadsafe.zip
>
>
> 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
time.
> 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: "}}
> * {{"*** CHECKSUM FAILED - RETRYING"}}



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

Mime
View raw message