From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

It's there: <https://plugins.gradle.org/m2/gradle/plugin/com/github/johnrengelman/shadow/>

The coordinates changed to
```classpath "gradle.plugin.com.github.johnrengelman:shadow:7.1.2"```
(you can see this in <https://plugins.gradle.org/plugin/com.github.johnrengelman.shadow|the plugin portal page>, legacy plugin application)

(Or open the pom file and follow the dependencies)

Aha! Thank you. Is this a systematic change to how Gradle 7 plugins are published?

Maybe? If it is, it's not systematic, <https://plugins.gradle.org/plugin/com.apollographql.apollo3|our plugin> is still published using the same group as ever.

OK. This plugin has had some inconsistent naming in the past (jengelman vs johnrengelman) so maybe the author's just been fixing that

Yep, it's in the <https://github.com/johnrengelman/shadow/blob/d8117e942b7d98e3274cb1cc9dbb4e4e978a2a58/src/docs/changes/README.md?plain=1#L12|CHANGELOG>

Other than, that, you could also simply use the plugin ID as dependency instead, then you are not affected of changes in the coordinates of the actual code artifact:
```&lt;plugin id&gt;:&lt;plugin id&gt;.gradle.plugin:&lt;plugin version&gt;```
That is also how plugins are resolved from the id in the `plugins { ... }` block