It is an old convention where all artifacts published to plugin portal had to have a group that starts with

gradle.plugin.

Actually the plugin in question has those coordinates until 3.2.1: https://plugins.gradle.org/m2/gradle/plugin/com/google/cloud/tools/jib-gradle-plugin/ And changed to the new coordinates thereafter: https://plugins.gradle.org/m2/com/google/cloud/tools/jib-gradle-plugin/

So maybe you have some manual id to artifact mapping where you still have the old coordinates but updated the version or something like that.

Actually you should usually not have that manual mapping, but just depend on the marker artifacts that translate plugin id to code artifact

I have that "manual mapping" because that's the only way to do it with convention plugins / platforms, as far as I know?

the project structure is based on https://docs.gradle.org/current/userguide/structuring_software_products.html, with

build-logic

and

platforms

that also clears up some confusion around why I always needed to look up these coordinates from the "legacy" sections on e.g. https://plugins.gradle.org/plugin/com.google.cloud.tools.jib 🙂 thanks!

seems like it'd be nice if the Gradle DSL had a built-in function to build that marker artifact coordinate from the plugin id, considering it's a bit redundant. but I just saw you had a similar idea a while ago already 😄 https://github.com/gradle/gradle/issues/9282#issuecomment-490219792