Search Gradle plugins
Plugin | Latest Version |
---|---|
se.patrikerdes.use-latest-versionsA plugin that updates the versions of your dependencies in your gradle project to the latest available versions. |
0.2.18
(31 October 2021) |
de.usr42.use-latest-versionsA plugin that updates the versions of your dependencies in your *.gradle files to the latest available versions. This plugin depends on the Gradle Versions Plugin. |
0.2.13
(25 October 2019) |
org.sirekanyan.version-checkerA Gradle plugin for checking the latest versions of dependencies |
1.0.12
(22 October 2024) |
io.github.turansky.kfc.latest-webpackConfigure latest/stable webpack for Kotlin/JS projects |
8.10.0
(11 August 2024) |
com.liferay.dependency.checkerThe Dependency Checker Gradle plugin lets you warn users if a specific configuration dependency is not the latest one available from the Maven central repository. The plugin eventually fails the build if the dependency age (the difference between the timestamp of the current version and the latest version) is above a predetermined threshold. |
1.0.6
(04 August 2023) |
com.github.turansky.kfc.latest-webpackConfigure latest/stable webpack for Kotlin/JS projects |
4.88.0
(03 February 2022) |
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) |
com.vaadinBuild Vaadin applications with Gradle. Please follow the link below to learn which Plugin version to use with particular Vaadin version. Vaadin recommends using the latest Vaadin LTS version. |
24.5.5
(18 November 2024) |
nl.littlerobots.version-catalog-updateProvides tasks to format and update the version catalog file with the latest dependency versions. |
0.8.5
(24 October 2024) |