# Does Travis centrally cache Maven artifacts?

**URL:** <https://travis-ci.community/t/does-travis-centrally-cache-maven-artifacts/8011>\
**Category:** Java\
**Tags:** build-env, java, bug\
**Created:** [April 6, 2020, 11:36am UTC](https://travis-ci.community/t/does-travis-centrally-cache-maven-artifacts/8011 "2020-04-06T11:36:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![adamretter](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/adamretter/32/837_2.png) [@adamretter](https://travis-ci.community/u/adamretter)\
**Post date:** [April 6, 2020, 11:36am UTC](https://travis-ci.community/t/does-travis-centrally-cache-maven-artifacts/8011/1 "2020-04-06T11:36:49Z")

</div>

We have started seeing strange issues in some of our builds which were otherwise fine.

```auto
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile (default-testCompile) on project exist-core: Compilation failure: Compilation failure: 
[ERROR] error reading /home/travis/.m2/repository/org/exist-db/thirdparty/com/ettrema/milton-api/1.8.1.3/milton-api-1.8.1.3.jar; error in opening zip file
[ERROR] error reading /home/travis/.m2/repository/org/exist-db/thirdparty/com/ettrema/milton-client/1.8.1.3/milton-client-1.8.1.3.jar; error in opening zip file
[ERROR] error reading /home/travis/.m2/repository/org/exist-db/thirdparty/com/ettrema/milton-api/1.8.1.3/milton-api-1.8.1.3.jar; error in opening zip file
[ERROR] error reading /home/travis/.m2/repository/org/exist-db/thirdparty/com/ettrema/milton-client/1.8.1.3/milton-client-1.8.1.3.jar; error in opening zip file

```

See - [https://travis-ci.com/github/eXist-db/exist/jobs/314882048#L335](https://travis-ci.com/github/eXist-db/exist/jobs/314882048#L335)

I know exactly what the issue is, but not how to solve it with Travis!

On [Maven Central](https://search.maven.org/) for a very short period of time the Jar files for Milton 1.8.1.3 were corrupt. We talked to Sontaype tech support and were able to have them taken down and replaced with the non-corrupt files. It seems that somehow Travis is pulling/caching the older corrupted Jar files.

Does Travis have a Maven proxy / Cache somewhere centrally where these need to be purged? I have tried clearing all our cached artifacts on Travis but this doesn’t seem to resolve the problem!

Please advise…

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [April 6, 2020, 4:27pm UTC](https://travis-ci.community/t/does-travis-centrally-cache-maven-artifacts/8011/2 "2020-04-06T16:27:56Z")

</div>

Last time I checked, Travis was using `google-maven-central`. See [Disable google-maven-central](https://travis-ci.community/t/disable-google-maven-central/5301).

Since you are running `mvn` with `-q`, silencing download information, can’t say if that’s still the case.