Search Gradle plugins

* Includes the foojay plugin for gradle 9 support of the toolchain api. * Auto imports sub projects. This also changes gradle to expect sub project's build.gradle.kts to be <sub project name>.gradle.kts. For example: * build.gradle.kts * settings.gradle.kts * my-service/my-service.gradle.kts * my-library/my-library.gradle.kts

• #conventions
• #settings

This plugin contains a bunch of best practices around how to build projects for the JVM. This includes dependency locking by default, kotlin support, groovy support (for testing), wiring up the junit platform, null away, and linting.

• #kotlin
• #java
• #groovy
• #conventions

SonarQube analysis integration. Conditionally applies org.sonarqube and configures sonar.host.url, sonar.token, sonar.projectKey (as '<group>:<name>'), sonar.projectName, and sonar.projectVersion. Silently skips (no sonarqube task is registered) when STANO_SONAR_HOST_URL or STANO_SONAR_TOKEN are not configured. Optionally enforces quality gate with build failure via com.stano.sonar.fail-build-enabled.

• #convention
• #sonarqube
• #code-quality

Docker container run lifecycle management. Registers dockerRun, dockerStop, dockerRemoveContainer, dockerRunStatus, and dockerNetworkModeStatus tasks. Configure the container via the dockerRun DSL: image, container name, ports, volumes, environment variables, command, network mode, and extra arguments. Supports daemonized containers (default) and ephemeral containers via clean=true (adds --rm).

• #convention
• #docker

Docker Compose file generation and lifecycle management. Registers generateDockerCompose (resolves artifact versions into a docker-compose.yml template), dockerComposeUp, and dockerComposeDown tasks. Configure the template path, output file, and token replacements via the dockerCompose DSL. Template tokens use {{group:name}} syntax and are resolved from the docker configuration or explicit templateToken(key, value) entries.

• #convention
• #docker
• #docker-compose

Extends com.stano.java for publishable library subprojects. Adds javadoc and sources JARs and configures Maven publishing to the private stano-maven repository (URL, username, and password from Gradle properties or STANO_MAVEN_URL / STANO_MAVEN_USERNAME / STANO_MAVEN_PASSWORD). Publishing is silently skipped when STANO_MAVEN_URL is not configured. Suppresses enforced-platform Gradle Module Metadata validation warnings.

• #convention
• #java
• #library
• #publishing

Core plugin for internal Java/Kotlin subprojects. Applies java-library, Kotlin JVM, JaCoCo, and Spotless (Google Java Format). Configures the Java toolchain from the root BaseExtension's javaVersion (default '21'). Configures tests with JUnit Platform and finalizes them with jacocoTestReport. When mspVersion is set, enforces the MSP BOM, excludes commons-logging and log4j, and auto-wires the MapStruct annotation processor when mapstruct is detected on the classpath. Requires com.stano.base (or com.stano.application) on the root project.

• #convention
• #java
• #kotlin
• #jacoco
• #spotless

Docker image build, tag, and push support. Registers docker (build), dockerTag, dockerPush, dockerLogin, dockerLogout, dockerClean, and dockerCleanupImage tasks. Configure images via the docker DSL: image name, Dockerfile path, build args, labels, platforms, and additional build context files. Supports docker buildx (default) with multi-platform builds and automatic AWS ECR login. Automatically stamps images with build provenance labels (branch, commit hash, build number, repository URL). When com.stano.spring-boot is also applied, auto-configures the image name and wires bootWar output as the build context.

• #convention
• #docker

Flyway is an open-source database migration tool. It strongly favors simplicity and convention over configuration. It is simple, focused and powerful. It runs on Windows, Mac OSX and Linux, Java and Android. It is based around just 6 basic commands: Migrate, Clean, Info, Validate, Baseline and Repair. Migrations can be written in SQL (database-specific syntax (such as PL/SQL, T-SQL, ...) is supported) or Java (for advanced data transformations or dealing with LOBs). It has a Command-line client. If you are on the JVM, we recommend using the Java API (also works on Android) for migrating the database on application startup. Alternatively, you can also use the Maven plugin, Gradle plugin, SBT plugin or the Ant tasks. And if that not enough, there are plugins available for Spring Boot, Dropwizard, Grails, Play, Griffon, Grunt, Ninja and more! Supported databases are Oracle, SQL Server, SQL Azure, DB2, DB2 z/OS, MySQL (including Amazon RDS), MariaDB, Google Cloud SQL, PostgreSQL (including Amazon RDS and Heroku), Redshift, Vertica, H2, Hsql Derby, SQLite and solidDB. More info: http://flywaydb.org

• #continuous delivery
• #flyway
• #database migrations
• #schema evolution

Applies org.springframework.boot and wires the MSP Spring Boot BOM for dependency management. Names the bootJar after the root project and registers copyOtelJavaagent to copy the OpenTelemetry Java agent into build/libs at assemble time. Adds spring-boot-devtools (developmentOnly), micrometer-registry-prometheus (runtimeOnly), msp-spring-boot-application (implementation), and msp-spring-test-starter (testImplementation). Rewrites application.yml at processResources time with build metadata (context name, version, CI environment). When com.stano.docker is also applied, auto-configures the Docker image name, build args, and wires bootWar output as the Docker build context.

• #convention
• #spring-boot
• #java