Search Gradle plugins
| Plugin | Latest Version |
|---|---|
com.netflix.nebula.plugin-pluginSets up publishing and release process for all of the other nebula plugins |
20.11.0
(09 January 2024) |
io.github.toxa2033.saved-stateKotlin compiler plugin generates support methods for use SaveStateHandle without constants and string variables. |
1.0.5
(08 June 2022) |
systems.manifold.manifold-gradle-pluginManifold is a Java compiler plugin, its features include Metaprogramming, Properties, Extension Methods, Operator Overloading, a Preprocessor, and a lot more. This Gradle plugin configures JavaCompile tasks to support the manifold compiler plugin. |
0.0.2-alpha
(24 September 2021) |
name.remal.maven-publish-gradle-plugin-portalPlugin that allows 'maven-publish' plugin publicate to Gradle Plugin Portal. |
1.5.0
(18 August 2021) |
name.remal.experimental-buildSrc-default-pluginsPlugin that applies buildSrc-default-plugins and name.remal.experimental-default-plugins plugins. |
1.5.0
(18 August 2021) |
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) |
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) |
org.embulk.embulk-pluginsA Gradle plugin to build and publish Embulk plugins |
0.7.0
(10 April 2024) |
com.huanshankeji.common-gradle-dependencies-dummy-pluginA dummy plugin defined to enable publishing the package to the Gradle Plugin Portal |
0.7.1-20240314-boostrap
(15 March 2024) |
dev.schlaubi.mikbot.gradle-pluginUtility plugin to build Mikbot and PF4J plugins |
3.29.0
(25 January 2024) |