[
https://issues.apache.org/jira/browse/MNG-6465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591568#comment-16591568
]
Lasse Westh-Nielsen commented on MNG-6465:
------------------------------------------
[~rfscholte] I am using a repository manager - Maven Central. I am just
downloading things via HTTP from Maven Central, nothing exotic.
I don't see what checksums would help with. The HTTP downloads fail with e.g.
status code 502. There _seems_ to be retries - I mean it is bog standard HTTP
stuff innit.
I just want to have extra many retries and maybe longer timeouts because I know
my problem domain: that intermittent HTTP downloads failing cause my builds to
fail.
> Artifact download failures
> --------------------------
>
> Key: MNG-6465
> URL: https://issues.apache.org/jira/browse/MNG-6465
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.5.0
> 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)
