maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MRESOLVER-55) Artifact download failures
Date Sat, 16 Feb 2019 19:56:00 GMT

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

Michael Osipov closed MRESOLVER-55.
-----------------------------------
       Resolution: Incomplete
    Fix Version/s:     (was: 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
>
> 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)

Mime
View raw message