Search Gradle plugins

Want to include your Gradle plugin here?

Plugin	Latest Version
io.github.crimix.changed-projects-task A Gradle plugin to run a user defined task on changed projects (modules) and their dependent projects (modules) #git #project dependencies #task #changed projects #changed modules	1.8 (29 October 2024)
io.github.appspiriment.project This project plugin simplifies the initial setup and version management for an Android application. It removes unnecessary configurations from the app module, creates the `appspirimentlibs.versions.toml` file corresponding to the plugin version, and adds the required `appspiriment` plugin exclusively to the app module (without affecting any other application modules or libraries). Additionally, the plugin configures the `appspirimentlibs.versions.toml` in the `settings.gradle.kts`. Note: If your project is using a `settings.gradle` file in Groovy, it will automatically convert it to the Kotlin DSL (`settings.gradle.kts`). You just need to add the plugin with correct version to the root build.gradle.kts (don't use alias, add it directly at first) and sync. This plugin is ideal for setting up a new project with a clean configuration or updating plugin versions. To update versions, simply update the project plugin version and sync. Be aware that this plugin will remove all configurations in the app module's Gradle file, so ensure that no additional configurations are lost. #android #settings #conventions	0.0.2 (20 January 2025)
io.github.bjoernmayer.gradle-project-dependents List dependents of your project in multi-projects #dependencies #multi-project	0.3.1 (15 November 2024)
io.github.gciatto.kt-mpp.multi-project-helper Kotlin multi-platform and multi-project configurations plugin for Gradle: multi-platform & multi-project helper plugin #kotlin #multi-platform	4.1.4 (31 May 2024)
io.github.gregoranders.project-configuration Following the principle of convention over configuration this Gradle plugin provides default configurations for various plugins of a Gradle JVM project so that you do not need to copy boilerplate code throughout your projects. #project #configuration #java #checkstyle #pmd #spotbugs #jacoco #dependencycheck	0.0.9 (04 June 2023)
org.taruts.workspace A plugin for workspace projects. A workspace project groups a number of related projects, each stored in a separate Git repository. This plugin automates cloning of projects included in a workspace for developers who start working with it. The DSL of the plugin allows to specify the list of projects in the workspace and to which subdirectories they are to be cloned. #workspace #group #automation #git #clone #subproject #child	1.0.3 (16 March 2023)
io.alcide.gradle-semantic-build-versioning This is a Gradle settings-plugin that provides support for semantic versioning of builds. It is quite easy to use and extremely configurable. The plugin allows you to bump the major, minor, patch or pre-release version based on the latest version, which is identified from a git tag. It also allows you to bump pre-release versions based on a scheme that you define. The version can be bumped by using version-component-specific project properties or can be bumped automatically based on the contents of a commit message. If no manual bumping is done via commit message or project property, the plugin will increment the version-component with the lowest precedence; this is usually the patch version, but can be the pre-release version if the latest version is a pre-release one. The plugin does its best to ensure that you do not accidentally violate semver rules while generating your versions; in cases where this might happen the plugin forces you to be explicit about violating these rules. As this is a settings plugin, it is applied to settings.gradle and version calculation is therefore performed right at the start of the build, before any projects are configured. This means that the project version is immediately available (almost as if it were set explicitly - which it effectively is), and will never change during the build (barring some other, external task that attempts to modify the version during the build). While the build is running, tagging or changing the project properties will not influence the version that was calculated at the start of the build. #versioning #semantic-versioning #git #build-versioning #auto-versioning #version	4.2.2 (13 May 2021)
com.trevorism.create-project Create standard folder structure, build file, and sample code with unit tests for a new project. #create project #java #groovy #scala	0.9.0 (28 October 2020)
javamuc.gradle-semantic-build-versioning This is a Gradle settings-plugin that provides support for semantic versioning of builds. It is quite easy to use and extremely configurable. The plugin allows you to bump the major, minor, patch or pre-release version based on the latest version, which is identified from a git tag. It also allows you to bump pre-release versions based on a scheme that you define. The version can be bumped by using version-component-specific project properties or can be bumped automatically based on the contents of a commit message. If no manual bumping is done via commit message or project property, the plugin will increment the version-component with the lowest precedence; this is usually the patch version, but can be the pre-release version if the latest version is a pre-release one. The plugin does its best to ensure that you do not accidentally violate semver rules while generating your versions; in cases where this might happen the plugin forces you to be explicit about violating these rules. As this is a settings plugin, it is applied to settings.gradle and version calculation is therefore performed right at the start of the build, before any projects are configured. This means that the project version is immediately available (almost as if it were set explicitly - which it effectively is), and will never change during the build (barring some other, external task that attempts to modify the version during the build). While the build is running, tagging or changing the project properties will not influence the version that was calculated at the start of the build. #versioning #semantic-versioning #git #build-versioning #auto-versioning #version	4.1.1 (26 July 2018)
nebula.rxjava-project Template for RxJava projects #nebula #rxjava #project	4.0.0 (10 February 2016)