Search Gradle plugins

Plugin Latest Version


gradle plugin for generate i18n message from source file written by javadoc.

(28 September 2021)


Gradle plugin that create tasks to post messages on Slack WebHook

(18 June 2019)


Gradle Plugin to scan the class path, pre-compile and pack message and template formats into a single file.

(09 June 2024)


Empressia Message Tasks by Empressia.

(12 May 2021)


Produces tests' output in Teamcity Service Message format

(25 August 2018)


A plugin that helps you send message to DingTalk

(27 May 2018)


This plugin provides tasks and conventions to send slack messages

(18 August 2023)


Gradle plugin that create tasks to post messages on Slack Webhook

(26 July 2022)


This plugin checks the Java version your Gradle build is running with. If the version is lower than the required minimum version or it exceeds the maximum version accepted, then the build is aborted with an friendly, easy to spot error message pointing towards the problem. This should help to avoid having to dig through the build output to find only to find an unsupported class file version error messages buried somehere in the output due to a bad Java runtime version.

(03 July 2022)


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)