Search Gradle plugins

Want to include your Gradle plugin here?

Plugin	Latest Version
uk.co.littlemike.git-tag-plugin Plugin for simple tagging of releases in git #simple #git #release #tag #tagging	0.2 (15 June 2016)
com.github.piddubnyi.gradle-git-tag-semantic-versioner Plugin for versioning multimodule project based on git tags #git #version	1.0 (18 May 2020)
com.es.em.am.tag It creates git tag same as version value defined in build file #git #tag	5.0.7 (16 July 2018)
com.corneliudascalu.autoversion Auto versioning based on the most recent git tag #versioning #git #tag	0.3 (12 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)
com.liferay.tlddoc.builder The TLDDoc Builder Gradle plugin lets you run the Tag Library Documentation Generator tool in order to generate documentation for the JSP Tag Library Descriptor (TLD) files in your project. #java #liferay #tld	1.3.4 (04 March 2020)
me.qoomon.git-versioning This extension will adjust the project version, based on current git branch or tag. #git #versioning #version #tag #branch #generated #artificial	3.0.0 (11 February 2020)
com.dorkbox.VersionUpdate Plugin to set version information in maven POM, java or kotlin files, and git tags #version #versioning #semver #semantic-versioning	1.6.1 (15 November 2019)
de.seewes.git.version Simple Plugin to set gradle version by git tag or branch name. #git #version #git tag	0.3 (13 November 2019)
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)