Did gradlePluginPortal upstream mirroring just change?

We publish the following to mavenCentral and to the Gradle plugin portal

It depends on these two libs, which we only publish to mavenCentral

On May 3rd 2022, we published plugin-gradle 6.5.2 which depends on lib 2.25.2. Users can use 6.5.2 without configuring any custom repositories.

On May 10th 2022, we published plugin-gradle 6.6.0 which depends on lib 2.25.3. When users try to use it, it fails with

> Could not find com.diffplug.spotless:spotless-lib:2.25.3.
  Searched in the following locations:
    - https://plugins.gradle.org/m2/com/diffplug/spotless/spotless-lib/2.25.3/spotless-lib-2.25.3.pom
  If the artifact you are trying to retrieve can be found in the repository but without metadata in 'Maven POM' format, you need to adjust the 'metadataSources { ... }' of the repository declaration.
  Required by:
      unspecified:unspecified:unspecified > com.diffplug.spotless:com.diffplug.spotless.gradle.plugin:6.6.0 > com.diffplug.spotless:spotless-plugin-gradle:6.6.0

The workaround is to add:

pluginManagement {
    repositories {

It’s strange that this workaround is needed for 6.6.0, but wasn’t needed for 6.5.2 - we made no changes to our publishing logic between these two releases.

Did something change about transitive dependencies and plugin portal?

See also: 2.25.3 is unavailable on Gradle repository · Issue #1203 · diffplug/spotless · GitHub


As replied on the GH issue:

Hey folks,

Sorry about that. The Gradle JCenter mirror had one timeout with a too high value. I believe that what happened is a request was made before JCenter itself had mirrored Maven Central - we have noticed delays there recently. And in that case, we were caching that miss for too long.
Issue has been fixed and the dependency can now be found.

1 Like