We released the latest version of our plugin this morning and it appeared to successfully published to the plugin portal. Now our main project build is failing with:
Could not find gradle.plugin.org.openrepose:gradle-jaxb-plugin:2.4.0.
A problem occurred evaluating root project 'java'.
> Could not resolve all files for configuration 'classpath'.
> Could not find gradle.plugin.com.zeroc.gradle.ice-builder:slice:1.4.2.
Searched in the following locations:
https://plugins.gradle.org/m2/gradle/plugin/com/zeroc/gradle/ice-builder/slice/1.4.2/slice-1.4.2.pom
https://plugins.gradle.org/m2/gradle/plugin/com/zeroc/gradle/ice-builder/slice/1.4.2/slice-1.4.2.jar
Trying to download the JAR with curl show 404 error
$ curl -LI 'https://plugins.gradle.org/m2/gradle/plugin/com/zeroc/gradle/ice-builder/slice/1.4.2/slice-1.4.2.jar'
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0HTTP/1.1 303 See Other
Date: Wed, 02 Aug 2017 18:50:17 GMT
Connection: keep-alive
Set-Cookie: __cfduid=de6981fc9d861949734dc60bd30e0af211501699817; expires=Thu, 02-Aug-18 18:50:17 GMT; path=/; domain=.gradle.org; HttpOnly
Location: https://plugins-artifacts.gradle.org/gradle.plugin.com.zeroc.gradle.ice-builder/slice/1.4.2/837648833442f754f8fa2ad89acc901c4e29ecd82e6b395e2a67e01306654009/slice-1.4.2.jar
Via: 1.1 vegur
CF-Cache-Status: HIT
Expires: Thu, 03 Aug 2017 06:50:17 GMT
Cache-Control: public, max-age=43200
Server: cloudflare-nginx
CF-RAY: 388338d34d2f2f71-MAD
HTTP/1.1 404 Not Found
Date: Wed, 02 Aug 2017 18:50:17 GMT
Content-Type: application/xml
Connection: keep-alive
Set-Cookie: __cfduid=d0f316843de35f8ad17e3f8c52c00bc4c1501699817; expires=Thu, 02-Aug-18 18:50:17 GMT; path=/; domain=.gradle.org; HttpOnly
x-amz-request-id: A09D63ED39E8E2AA
x-amz-id-2: lHjylIAFmSnzXNSZ3kDh/tfi6DjoCHxrmRVt1B6FzcCz5RgMxysHPAcKpXQGwAXqXgk9BQZXTQk=
CF-Cache-Status: HIT
Server: cloudflare-nginx
CF-RAY: 388338d49d3f5456-MAD
I testing other plug-ins published today and seems it is affecting many of them with similar errors
A problem occurred configuring root project 'java'.
> Could not resolve all files for configuration ':classpath'.
> Could not find gradle.plugin.com.vanniktech:gradle-code-quality-tools-plugin:0.7.0.
Searched in the following locations:
https://plugins.gradle.org/m2/gradle/plugin/com/vanniktech/gradle-code-quality-tools-plugin/0.7.0/gradle-code-quality-tools-plugin-0.7.0.pom
https://plugins.gradle.org/m2/gradle/plugin/com/vanniktech/gradle-code-quality-tools-plugin/0.7.0/gradle-code-quality-tools-plugin-0.7.0.jar
Required by:
project :
What went wrong:
A problem occurred configuring root project ‘java’.
@PeponeOnrez@repose-bot Some plugins are being published ok, so I’m trying to narrow down what’s different about these ones. Do you have any logs from the builds that published those plugin versions? I would also be very interested in knowing the plugin-publish plugin version that is being used. We fixed a bug in 0.9.7 where errors from artifact upload were ignored.
Some further investigation: it looks like plugins not uploading artifacts are all using older versions of the plugin-publish plugin. The most recent version fixed a couple of bugs that are leading to this, including not detecting failed uploads correctly. This means that those artifacts were never published, unfortunately.
We’ll put some measures in place to ensure that new plugin versions can’t get activated without all of the expected artifacts getting uploaded successfully, but in the meantime we’ll have to deal with the broken state of the recently-uploaded plugins.
The fix will be for us to remove those versions from the portal and have you re-publish them, after upgrading the plugin-publish plugin to 0.9.7. I have deleted the two broken versions reported in this thread so far, please report any other that you find.
Glad it was something easy enough to figure out and get fixed. I’m part of the Repose team that started this original thread and the failed publish was using:
com.gradle.publish:plugin-publish-plugin:0.9.5
Thanks for deleting that failed version and we will update the version being used and re-publish shortly.
Also thanks for the quick response. Keep up the great work guys.
I accidentally republished the gradle-jaxb-plugin v2.4.0 using the plugin-publish-plugin v0.9.5 and guess what, it failed again. Gotta love consistency. I did update the plugin-publish-plugin to v0.9.7 and successfully published gradle-jaxb-plugin v2.4.1.
I we could get the bad gradle-jaxb-plugin v2.4.0 removed again, that would be great.