[
https://issues.apache.org/jira/browse/MNG-6465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591577#comment-16591577
]
Robert Scholte commented on MNG-6465:
-------------------------------------
Maven Central it not *_your_* repository manager. I would expect an Archiva,
Artifactory or Nexus, which is connected to Maven Central. This repository
manager is installed within your infra and acts like the cache you are looking
for. So your builds are not downloading direcly from Central anymore, but from
this manager.
> 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)
