Search Gradle plugins
| Plugin | Latest Version |
|---|---|
com.sandpolis.build.pluginThis plugin applies configuration for building Sandpolis plugins |
0.3
(28 November 2021) |
sap.commerce.build.ccv2Use the CCv2 manifest.json to configure and build your local development environment |
4.0.0
(01 August 2023) |
org.kordamp.gradle.build-infoDefines common build properties |
0.54.0
(26 December 2023) |
mpern.sap.commerce.build.ccv2Use the CCv2 manifest.json to build and configure your local development environmennt |
2.1.1
(25 September 2020) |
org.siouan.frontend-jdk11Build frontend applications with Node, NPM, Yarn: distribution management, configurable tasks (build, test, publish), additional types, support of NPX. |
8.0.0
(24 August 2023) |
org.siouan.frontend-jdk8Build frontend applications with Node, NPM, Yarn: distribution management, configurable tasks (build, test, publish), additional types, support of NPX. |
6.0.0
(07 November 2021) |
com.ekino.oss.gradle.plugin.javaJava plugin applying some configuration for your builds (mavenPublish, testSets, etc ...) |
2.0.0
(10 August 2021) |
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) |
io.alcide.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.2.2
(13 May 2021) |
io.cloudflight.autoconfigure.report-configurePreconfiguring reports for your build |
1.1.1
(11 December 2023) |