Since around 1 week there has been some issues with Maven central repo denying access to Travis builds (see Continuous maven repo 403).
The fix as of today consists in using google mirror of Maven central. However using this mirror, I get checksum validation failures in some of my builds. This include, for instance, the preesm/graphiti project, with :
I could reproduce locally playing with local maven settings (https://stackoverflow.com/a/4997553 ). When I use the default central repository, the build runs fine.
Below are 2 notes about the current build failures of the Graphiti project on travis:
Note: Since less than 1 week, Oracle certificates expired (or something is wrong with travis openjdk9 setup script), leading to failures way before the one described in first post. This does not happen if build is triggered somewhere else.
Note2: Also, the main Eclipse mirror used to build the project (the only French Eclipse mirror, closest to the work place) went down few days ago, also leading to failures before the one described in first post. Latest updates on the graphiti github repo develop branch includes the fix to use another (still online) mirror.
I’ll look into the missing files – if that’s all it is, I should be able to fix in an hour or two, but figuring out why might take longer. Will update the issue in 30 min.
Our VMs start with a base image with nothing in ~/.m2, so I am doubtful that the cache comes into play. It is possible to run mvn with -X; it is best done by @antoine-morvan by tweaking .travis.yml.
Even locally I clear my cache before change the remote repos to make sure other people can continue build the project anywhere. And the travis build do not cache the local repo either to enforce that behavior.
Also, in case you missed it, the build script uses the -C option : “-C,–strict-checksums : Fail the build if checksums don’t match”.
@lesv Clearing repo and running again locally. Updating soon with result.
@lesv Still failing locally with cleared repo and google as mirror of central:
Could not transfer artifact org.apache.maven.reporting:maven-reporting-impl:pom:2.3 from/to google-maven-central (https://storage-download.googleapis.com/maven-central/repos/central/data/): Checksum validation failed, no checksums available -> [Help 1]
I running out of the office today, and will be out for a few days for the holidays. You might wish to roll back to using the maven-central repo for now.
I’ve ping’d the central-discussions list again, no one responded to my last email. I’m going to run a few experiments to see if I can use a different source and get this fixed. It will take several days as what I’m dealing with is huge.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.0.0:check (default) on project tyrus-project: Execution default of goal org.apache.maven.plugins:maven-checkstyle-plugin:3.0.0:check failed: Plugin org.apache.maven.plugins:maven-checkstyle-plugin:3.0.0 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-checkstyle-plugin:jar:3.0.0 -> org.apache.maven.reporting:maven-reporting-impl:jar:2.3: Failed to read artifact descriptor for org.apache.maven.reporting:maven-reporting-impl:jar:2.3: Could not transfer artifact org.apache.maven.reporting:maven-reporting-impl:pom:2.3 from/to google-maven-central (https://maven-central.storage-download.googleapis.com/repos/central/data/): Checksum validation failed, no checksums available -> [Help 1]
Sorry - I spoke too soon. It appears my sync between my VM and the bucket got killed just after midnight, I’ve restarted it, but it takes a while to process 12T. I’ll let you know when it’s actually done.
For the time being, don’t use checksum’s using mvn -C
Going forward Sonatype is working on a new source repository for me to use, I will also let you know when that is completed.
Builds of new branches (1.15-BRANCH) get passed the checksum verification now (as you can see here https://travis-ci.org/nuessgens/tyrus/builds/560619011)… at least until it is terminated because “the job exceeded the maximum log length”
[ERROR] Plugin org.codehaus.mojo:build-helper-maven-plugin:1.8 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.codehaus.mojo:build-helper-maven-plugin:jar:1.8: Could not transfer artifact org.codehaus.mojo:build-helper-maven-plugin:pom:1.8 from/to google-maven-central (https://maven-central.storage-download.googleapis.com/repos/central/data/): Checksum validation failed, expected dfc6267db807f9c21415b7eef50137742e99c364 but is 74a16507270d0d85a77b15b5f5e97010d193cb9b -> [Help 1]
Any Idea how I can start over with this branch (I already tried deleting caches without any luck)
@BanzaiMan can give you suggestions on the right way to do this. What you are trying for is effectively mvn clean; rm -r ~/.m2
FYI: My update job is still running, so more checksums are correct, but it’s not complete yet. I’ll need to do some cleanup / validation once it finishes.
I’m afraid the checksums are still wrong.
I tried removing the whole $HOME/.m2 folder (which resulted in downloading the artifacts from maven-central) as well as just removing $HOME/.m2/repository.
It seems the cached checksums are note the problem but rather the checksums returned by the maven-central.storage-download.googleapis.com-Mirror
