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

Gradle Community

Snippet to make plugin deps easier: <https://gradle-community.slack.com/archives/CAHSN3LDN/p1678816316527139?thread_ts=1678816171.009059&amp;channel=CAHSN3LDN&amp;message_ts=1678816316.527139|https://gradle-community.slack.com/archives/CAHSN3LDN/p1678816316527139?thread_ts=1678816171.009059&amp;channel=CAHSN3LDN&amp;message_ts=1678816316.527139>

And here the according documentation: <https://docs.gradle.org/current/userguide/plugins.html#sec:plugin_markers>

the `.gradle.plugin` suffix comes from the Gradle Plugin Marker.

<https://docs.gradle.org/8.1.1/userguide/plugins.html#sec:plugin_markers>

```${plugin.id}:${plugin.id}.gradle.plugin:${plugin.version}```
So if the plugin ID is `org.jetbrains.kotlin.jvm`, then the Maven Coordinates of the plugin marker are

```org.jetbrains.kotlin.jvm:org.jetbrains.kotlin.jvm.gradle.plugin:$version```
And that Maven artifact will be empty, except for a POM that has a dependency on the _actual_ plugin JAR, which has the coordinates

```org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlinVersion```
