You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Stop publishing redirect artifacts at com.diffplug.gradle.spotless #2844
Add this plugin to your build using the [plugins DSL](https://docs.gradle.org/current/userguide/plugins.html#sec:plugins_block):
plugins {
id("com.diffplug.gradle.spotless") version "8.2.1"
}
if you do that you get:
Caused by: org.gradle.api.GradleException: We have moved from 'com.diffplug.gradle.spotless'
to 'com.diffplug.spotless'
To migrate:
- Test your build with: id 'com.diffplug.gradle.spotless' version '4.5.1'
- Fix any deprecation warnings (shouldn't be many / any)
- Now you can use: id 'com.diffplug.spotless' version '5.0.0'
It's not possible for us to remove the old id from the portal, which is why we always publish to both points (and give a nice error message). But after all these years, it's probably okay for us to stop publishing to the old id.
I see that the deprecated artifact shows up first in the search. It's first alphabetically, but hopefully we stop publishing it will start to fall.
changed the title [-]Gradle plugin portal has obsolete plugin id[/-][+]Stop publishing redirect artifacts at `com.diffplug.gradle.spotless`[/+]on Jan 30, 2026
Is this one already resolved? It looks like #3086 removed the legacy com.diffplug.gradle.spotless plugin marker, and it shipped in plugin-gradle 8.10.3 (CHANGES.md: "We no longer publish a plugin marker for the legacy com.diffplug.gradle.spotless id…").
The Plugin Portal metadata seems to agree: the com.diffplug.gradle.spotless marker stops at 8.10.2, while com.diffplug.spotless continued with 8.10.3 and 8.11.0. The in-jar redirect (SpotlessPluginRedirect) is still there, so anyone applying the old id from the buildscript classpath still gets the migration message.
If I'm not missing anything, could this be closed as completed?
Activity
nedtwigg commentedon Jan 30, 2026
It's not possible for us to remove the old id from the portal, which is why we always publish to both points (and give a nice error message). But after all these years, it's probably okay for us to stop publishing to the old id.
I see that the deprecated artifact shows up first in the search. It's first alphabetically, but hopefully we stop publishing it will start to fall.
[-]Gradle plugin portal has obsolete plugin id[/-][+]Stop publishing redirect artifacts at `com.diffplug.gradle.spotless`[/+]Pankraz76 commentedon Nov 8, 2026
Is this one already resolved? It looks like #3086 removed the legacy
com.diffplug.gradle.spotlessplugin marker, and it shipped in plugin-gradle 8.10.3 (CHANGES.md: "We no longer publish a plugin marker for the legacycom.diffplug.gradle.spotlessid…").The Plugin Portal metadata seems to agree: the
com.diffplug.gradle.spotlessmarker stops at 8.10.2, whilecom.diffplug.spotlesscontinued with 8.10.3 and 8.11.0. The in-jar redirect (SpotlessPluginRedirect) is still there, so anyone applying the old id from the buildscript classpath still gets the migration message.If I'm not missing anything, could this be closed as completed?