You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/09/25 18:38:00 UTC

[jira] [Commented] (MRESOLVER-55) Artifact download failures

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

Michael Osipov commented on MRESOLVER-55:
-----------------------------------------

Log files please. I haven't seen anything confirming a bug in Aether or Wagon. Even if, I consider it to be in Wagon.

bq. separately though it would be great to be able to configure retries and timeouts for dependency downloads

Wagon offers most of that and the upcoming version will cover all of them.

> Artifact download failures
> --------------------------
>
>                 Key: MRESOLVER-55
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-55
>             Project: Maven Resolver
>          Issue Type: Bug
>          Components: resolver
>    Affects Versions: Maven Artifact Resolver 1.1.1
>         Environment: Windows, Ubuntu
>            Reporter: Lasse Westh-Nielsen
>            Priority: Major
>             Fix For: waiting-for-feedback
>
>
> Hey,
> We often run Maven builds of [https://github.com/neo4j/neo4j] on machines with cold caches/ empty ~/.m2/repository folders.
> There are rather a lot of dependencies to download, so even though the failure rate of individual artifact downloads is small, at our scale it causes significant build failures.
> I am working on seeding caches. Separately though it would be great to be able to configure retries and timeouts for dependency downloads - optimise for build throughput rather than latency as it were.
> How do I do that? I can't find it documented anywhere, and trying to browse "wagon" source code got me nowhere.
> Regards,
> Lasse
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)