Search Gradle plugins
| Plugin | Latest Version |
|---|---|
calces.modulesAndroid componentized automatic build script |
3.3.0-alpha01
(14 December 2018) |
calces.appconfigAndroid componentized automatic build script |
3.3.0-alpha01
(14 December 2018) |
at.karriere.versionThe karriere.at version plugin for automatic versioning. |
1.3.2
(13 December 2018) |
net.bjoernpetersen.visitorgenAn automatic Visitor generator for Java |
0.5.1
(28 November 2018) |
all.shared.gradle.code-common-tasksA Common Set of Gradle's Tasks for Backend's and Frontend's Development<br> automatically applied |
1.0.1
(10 November 2018) |
com.mreil.autoconfOpinionated default plugin configuration |
0.0.5
(16 October 2018) |
com.bcombes.tinypngGradle plugin for automatically optimizing project png and jpg images! |
1.3
(28 September 2018) |
org.spongepowered.metaGradle plugin automatically generating a mcmod.info metadata file with the project properties |
0.9.0
(27 August 2018) |
javamuc.gradle-semantic-build-versioningThis 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. |
4.1.1
(26 July 2018) |
com.rhtech.springbootversionAutomatically Manages Version For Spring Boot Applications! |
1.0
(30 March 2018) |