Search Gradle plugins

Want to include your Gradle plugin here?

Plugin	Latest Version
io.github.noproxy.android-plugin-kit-plugin A plugin to help developing gradle plugin based on android Gradle Plugin. #gradle plugin development #android	0.0.2 (14 August 2019)
com.iadams.gradle-plugin-plugin An (opinionated) plugin for creating gradle plugins. #gradle-plugin	0.2 (07 December 2015)
name.remal.experimental-default-plugins Plugin that applies name.remal.default-plugins plugin and default experimental plugins (see full docs for a list of the plugins). #common #default #experimental	1.0.191 (19 May 2020)
name.remal.maven-publish-gradle-plugin-portal Plugin that allows 'maven-publish' plugin publicate to Gradle Plugin Portal. #gradle #plugin #publish #publication #maven #maven-publish	1.0.191 (19 May 2020)
name.remal.experimental-buildSrc-default-plugins Plugin that applies buildSrc-default-plugins and name.remal.experimental-default-plugins plugins. #common #default #buildsrc #experimental	1.0.191 (19 May 2020)
io.freefair.maven-plugin A Gradle plugin for building maven plugins #maven-plugin	5.1.0 (15 May 2020)
de.benediktritter.maven-plugin-development Gradle plugin for developing Apache Maven plugins #maven #mojo #maven plugin	0.2.1 (02 May 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.1 (07 April 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)
name.remal.root-project-default-plugins Plugin that applies many different plugins by default to the root project. See documentation for full applied plugins list. #common #default	1.0.191 (19 May 2020)