🐘 Common Build Plugins

Common project and settings gradle convention plugin to bootstrap Kotlin JVM & Multiplatform projects.

Install Java 21

$ curl -s "https://get.sdkman.io" | bash
$ sdk i java 21.0.5-zulu
$ sdk u java 21.0.5-zulu

Build & Testing

$ ./gradlew build

For testing, a separate sandbox project is available with the plugin and version catalog applied in settings.gradle.kts. First publish the plugin to the local maven repository and then run the sandbox project.

$ ./gradlew publishToMavenLocal
$ ./gradlew -p sandbox :build
$ ./gradlew -p sandbox :dependencyUpdates

Publishing

Push a new tag to trigger the release workflow and publish the plugin to maven central. That's it 🎉. The next version will be based on the semantic version scope (major, minor, patch)

$ ./gradlew pushSemverTag "-Psemver.scope=patch"

# To see the current version
# ./gradlew v

# Print the new version
# ./gradlew printSemver "-Psemver.scope=patch"

Published Plugins

Gradle Plugin ID	Version
dev.suresh.plugin.root
dev.suresh.plugin.common
dev.suresh.plugin.graalvm
dev.suresh.plugin.kotlin.jvm
dev.suresh.plugin.kotlin.mpp
dev.suresh.plugin.kotlin.docs
dev.suresh.plugin.kotlin.benchmark
dev.suresh.plugin.publishing
dev.suresh.plugin.repos
dev.suresh.plugin.catalog

Verifying Artifacts

The published artifacts are signed using this key. The best way to verify artifacts is automatically with Gradle.

Misc

Maven Central

• Publishing

  # Publish to local maven repository
  $ ./gradlew publishToMavenLocal
  $  tree  ~/.m2/repository/dev/suresh/build/
  
  # Publish the plugins to maven central
  $ ./gradlew publishPluginMavenPublicationToMavenCentralRepository
  
  # Publish the catalog to maven central
  $ ./gradlew :catalog:publishToMavenCentral
  $ ./gradlew :catalog:publishAndReleaseToMavenCentral