Hello, Szczepan! Thanks for writing in about this, I‘m glad to hear that Travis CI plays a part in releasing something that so many people work with.{#HS:345536156-51956#}
I’m not that familiar with Java dependency management in the modern era, as I’m primarily in Javascript/Elixir spaces now. But I found this thread showing a similar error, though the root of that was the project maintainer’s use of a Let’s Encrypt certificate, which isn’t the case for plugins.gradle.org. However, the comments suggesting that things work with newer versions of Java and that being also true in your case make me wonder whether something similar is applicable here.
Similarly, in this Travis-specific thread, people are having more success on Java 7 and newer.
Can you let me know some things:It would seem an unfortunate compromise to use HTTP-only dependencies, but knowing whether it works would help get us closer to understanding the problem.
- are you able to get the dependencies loaded locally when running Java 6?
- is it possible to have Gradle use HTTP-only dependencies, as suggested here?
How would you rate my reply?
Great Okay Not Good
--
Buck Doyle
Travis Builder
sup...@travis-ci.com
Visit https://www.traviscistatus.com/ for service status and uptime details
—
Travis CI GmbH, Rigaer Str.8, 10247 Berlin, Germany | GF/CEO: Mathias Meyer, Joshua Kalderimis | Contact: con...@travis-ci.org | Amtsgericht Charlottenburg, Berlin, HRB 140133 B | Umsatzsteuer-ID gemäß §27 a Umsatzsteuergesetz: DE282002648