Search Gradle plugins

Plugin Latest Version


Auto-generates version class file using Git and Gradle

(30 January 2019)


A plugin that allows auto-generating provider configuration files necessary to use Java Service Provider Interface functionality

(04 August 2017)


Gradle Configuration Plugin

(02 April 2017)


A Gradle plugin to generate the module graph and include the modules

(06 September 2020)

A kotlin compiler plugin to generate toString().

(03 April 2021)

Release tools and Gradle plugins that automate Mockito continuous delivery.

(07 July 2017)

Release tools and Gradle plugins that automate Mockito continuous delivery.

(29 May 2017)


This Kotlin file is autogenerated from a txt file where you only copy and paste the dependencies

(17 April 2020)


An easy Gradle plugin that follows rules to automatically generate the Patch version, Build number and Code version, while Major, Minor and Pre-Release suffix remain under our control.

(01 October 2019)


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.

(13 May 2021)