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:36:00 UTC

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

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

Michael Osipov updated MRESOLVER-55:
------------------------------------
    Fix Version/s: waiting-for-feedback

> 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)