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)
info.offthecob.Settings * 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	1.0.17 (11 July 2024)
dev.adamko.kotlin.binary-compatibility-validator.project Validates the public JVM binary API to make sure breaking changes are tracked. This is a Gradle Project plugin and can be applied in a `build.gradle` or `build.gradle.kts` file. #kotlin #kotlin/jvm #api-management #binary-compatibility	0.1.0 (02 May 2023)
com.linecorp.recursive-git-log-plugin A plugin for extract affected change log via git history and gradle project dependency #multi-project #multi-application #history #git	1.1.1 (24 March 2020)
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)
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)
com.wandera.affected-module-detector A plugin to detect modules with code change in a multi-module project #module #android #detection	0.1.0 (08 October 2024)
io.mateo.cxf-codegen View the project's changelog for any notable changes. #cxf #wsdl2java	1.2.1 (23 April 2023)
com.liferay.change.log.builder The Change Log Builder Gradle plugin lets you generate and maintain a change log file based on the Git commits in your project. #changelog #docs #documentation #git #liferay	1.1.7 (21 August 2023)
com.github.johnrengelman.shadow A Gradle plugin for collapsing all dependencies and project code into a single Jar file. NOTE: This plugin changed the core maintainer and has new coordinates: https://plugins.gradle.org/plugin/com.gradleup.shadow #onejar #shade #fatjar #uberjar	8.1.1 (20 March 2023)