[ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check (check-checkstyle) on project org.ietr.graphiti.parent: Execution check-checkstyle of goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check failed: Plugin org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-checkstyle-plugin:jar:3.1.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]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check (check-checkstyle) on project org.ietr.graphiti.parent: Execution check-checkstyle of goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check failed: Plugin org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-checkstyle-plugin:jar:3.1.0 ā org.apache.maven.reporting:maven-reporting-impl:jar:2.3
Iāve verified the data exists and appears correct on the mirror. Iām still concerned about the @smowton connection issue. If possible, could you re-run w/ mvn -X and paste the errors into a message?
Weāve worked around it by forcing the Maven mirror to Sonatypeās repository, since they fixed the original whitelisting problem. Therefore weāre unlikely to be able to provide a useful log, not that it showed anything more interesting than a bunch of fetches followed by a reset. There were two Maven processes running concurrently at the time, so according to default settings max 10 concurrent threads; lots of artefacts had been downloaded by that point so presumably each connection was being pipelined a bunch. Our other similar repository with only one concurrent Maven process did not exhibit the problem, so Iād guess at a threshold on requests per apparent origin per second, but canāt be sure. I tried replicating this by spamming curl requests but couldnāt elicit anything.
Exception in thread "main" java.io.IOException: Server returned HTTP response code: 403 for URL: https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.5.0/apache-maven-3.5.0-bin.zip
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1894)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263)
at org.apache.maven.wrapper.DefaultDownloader.downloadInternal(DefaultDownloader.java:73)
at org.apache.maven.wrapper.DefaultDownloader.download(DefaultDownloader.java:60)
at org.apache.maven.wrapper.Installer.createDist(Installer.java:64)
at org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:121)
at org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:50)
$ ./mvnw -v Downloading https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.5.0/apache-maven-3.5.0-bin.zip Exception in thread "main" java.io.IOException: Server returned HTTP response code: 403 for URL: https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.5.0/apache-maven-3.5.0-bin.zip at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1894) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263) at org.apache.maven.wrapper.DefaultDownloader.downloadInternal(DefaultDownloader.java:73) at org.apache.maven.wrapper.DefaultDownloader.download(DefaultDownloader.java:60) at org.apache.maven.wrapper.Installer.createDist(Installer.java:64) at org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:121) at org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:50) The command "./mvnw -v" failed and exited with 1 during .
To workaround this issue, I moved my repository url over to Googleās mirror (https://maven-central.storage-download.googleapis.com/repos/central/data/), as mentioned by @BanzaiMan above.
Actually, take a look at https://maven-central.storage.googleapis.com/index.html ā the path was updated a few months ago (and now updates every 2 hours), and Iāve stopped maintaining the repos/central/data/ path this weekend.
Which should be the default for Travis builds. Itās my understanding that if you havenāt cleared your build cache in a while you might not be using the correct path.
Also, if there is a problem with the GCS based maven-central mirror, please email gcs-maven-mirror@googlegroups.com as it has special filters that push me to see the issue faster. (I missed the email this morning - sorry)
Is this nat.travisci.net list maintained? I am using it as a security control, and am regularly having failures, where the IP assigned to the build env is not reflected in this ip list. Is there a frequency that this gets updated?