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

Gradle Community

Gradle uses so-called "plugin marker artifacts": <https://docs.gradle.org/current/userguide/plugins.html#sec:plugin_markers>
It maps the plugin ID to Maven groupId and artifactId, which should resolve to a component that will add the actual component as a dependency.

More information about publishing plugins: <https://docs.gradle.org/current/userguide/java_gradle_plugin.html#maven_publish_plugin>

It is my understanding that running this task would publish all "plugin maker artefacts", correct ?
`publishToMavenLocal - Publishes all Maven publications produced by this project to the local Maven cache.`

Assuming you used the java-gradle-plugin that declares them, then yes. You should then see `com/veepee/kotlin/android/application/com.veepee.kotlin.android.application.gradle.plugin/` and `com/veepee/android/test/android/application/com.veepee.android.test.android.application.gradle.plugin/` in your repository.
(of course you need to include a version somewhere in the consuming project, e.g.: `id ("com.veepee.kotlin.android.application") version "0.0.1"`)

Thank you Thomas! I was able to publish my plugins!