Search Gradle plugins
| Plugin | Latest Version |
|---|---|
io.github.kmbisset89.changelog.pluginThis plugin helps create a CHANGELOG file based on conventional commits. It is driven by a JSON formatter that will be improved in future versions. |
1.0.4
(02 February 2023) |
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) |
com.ismaeldivita.changetrackerA gradle plugin to track changes on modules and his dependents |
0.8.2
(26 February 2021) |
com.github.lanchon.dexpatcher.patch-libraryThe DexPatcher Patch Library plugin produces a DexPatcher patch library file that bundles compiled changes and additions to code and resources of a source application imported as a DexPatcher APK library, without bundling any part of the source application itself. The file is similar in structure to an Android library (AAR) file. The changes bundled in a patch library can be applied to the source application using the DexPatcher Patched Application plugin. Several patch libraries can be applied in the same step, or their application can be serialized though the cyclic use of the APK Library and Patched Application plugins. DexPatcher is free software. (GPLv3+) |
2.0.0
(31 October 2019) |
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.jooby.openAPIJooby is a modern, performant and easy to use web framework for Java and Kotlin built on top of your favorite web server. The joobyRun task allows to restart your application on code changes without exiting the JVM |
3.0.10
(16 April 2024) |
io.jooby.runJooby is a modern, performant and easy to use web framework for Java and Kotlin built on top of your favorite web server. The joobyRun task allows to restart your application on code changes without exiting the JVM |
3.0.10
(16 April 2024) |
io.github.leandroborgesferreira.dag-commandUnit tests only the changed modules in the dependencies graph |
1.11.0
(17 March 2024) |
nl.recognize.liquibase.validate.gradleA plugin for checking Liquibase changes |
1.0.8
(13 October 2023) |
info.offthecob.Settings* Includes the foojay plugin for gradle 9 support of the toolchain api. * Auto imports sub projects. This also changes gradle to expect sub project's build.gradle.kts to be <sub project name>.gradle.kts. For example: * build.gradle.kts * settings.gradle.kts * my-service/my-service.gradle.kts * my-library/my-library.gradle.kts |
1.0.15
(01 October 2023) |