maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lasse Westh-Nielsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MRESOLVER-54) Artifact download failures
Date Fri, 24 Aug 2018 14:06:00 GMT

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

Lasse Westh-Nielsen commented on MRESOLVER-54:
----------------------------------------------

This is a duplicate of https://issues.apache.org/jira/browse/MNG-6465, I was directed here
from there.

> Artifact download failures
> --------------------------
>
>                 Key: MRESOLVER-54
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-54
>             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 source code
got me nowhere.
> Regards,
> Lasse
>  



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

Mime
View raw message