Search Gradle plugins
Plugin | Latest Version |
---|---|
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) |
emetriq.changelog-releaseCreating a semi-automatic changelog on top of nebula release plugin |
1.4.0
(29 December 2017) |
com.github.deckyfx.gdgengradleCreate greendao3 Model automatically on build its read from JSON file schema, and also handle version upgrade migration |
1.0.8
(12 May 2019) |
io.github.appspiriment.roomThis plugin simplifies the setup of Room for an Android module by automatically applying the required libraries and configurations. It fetches the necessary Room versions from the `appspirimentlibs.versions.toml` file, so ensure that this file is present in your project before applying the plugin. Once applied, the plugin configures the module with all the dependencies and settings needed to integrate Room seamlessly. This helps streamline the setup process, ensuring consistency and compatibility with the versions specified in your `appspirimentlibs.versions.toml` file. |
0.0.3
(25 February 2025) |
com.legyver.legacy-java-module-infoCreate modular versions of dependencies of legacy libraries for modular applications. Heavily based on https://docs.gradle.org/current/samples/sample_java_modules_with_transform.html |
1.0.0
(27 November 2022) |
com.github.rewolf.gradle.moarjavadocAssists Javadoc tasks by automatically delomboking lombok'd source and linking Official Java SE Javadoc for the specified source version. |
1.0.0
(09 May 2020) |
io.github.appspiriment.projectThis project plugin simplifies the initial setup and version management for an Android application. It removes unnecessary configurations from the app module, creates the `appspirimentlibs.versions.toml` file corresponding to the plugin version, and adds the required `appspiriment` plugin exclusively to the app module (without affecting any other application modules or libraries). Additionally, the plugin configures the `appspirimentlibs.versions.toml` in the `settings.gradle.kts`. **Note:** If your project is using a `settings.gradle` file in Groovy, it will automatically convert it to the Kotlin DSL (`settings.gradle.kts`). You just need to add the plugin with correct version to the root build.gradle.kts (don't use alias, add it directly at first) and sync. This plugin is ideal for setting up a new project with a clean configuration or updating plugin versions. To update versions, simply update the project plugin version and sync. Be aware that this plugin will remove all configurations in the app module's Gradle file, so ensure that no additional configurations are lost. |
0.0.3
(25 February 2025) |