Search Gradle plugins

Want to include your Gradle plugin here?

Plugin	Latest Version
nebula.resolution-rules-producer Produces a resolution rules file tp be consumed by 'nebula.resolution-rules' #nebula #resolve #resolution #rules	1.5.1 (13 May 2016)
com.netflix.nebula.resolution-rules Gradle resolution rules plugin #nebula #resolve #resolution #rules	11.2.0 (03 October 2023)
nebula.resolution-rules Gradle resolution rules plugin #nebula #resolve #resolution #rules	9.0.0 (05 October 2021)
org.mikeneck.rule-based-model-generation This is plugin for Gradle, which generates interfaces for rule base model. #rule-based-model-configuration	0.3.0 (24 August 2015)
com.breskeby.lint.rules Additional Lint rules on top of the nebula.lint plugin #lint #formatting	0.0.1 (10 November 2016)
com.fizzpod.sweeney Gradle plugin providing ability to enforce build rules. #sweeney #enforce #rules	4.6.13 (25 April 2024)
com.github.zetten.bazel-dependencies-plugin A Gradle plugin that allows the generation of Bazel repository rules from Gradle project dependency configuration #bazel #dependencies #compatibility	3.0.1 (23 January 2024)
com.societegenerale.commons.arch-unit-gradle-plugin A Gradle plugin to run packaged ArchUnit rules #archunit	4.0.0 (17 November 2023)
io.github.noproxy.android-consumer-proguard-filtering-plugin A plugin to filter consumer proguard rules for Android #android #proguard	0.0.2 (08 April 2022)
io.alcide.gradle-semantic-build-versioning This 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. #versioning #semantic-versioning #git #build-versioning #auto-versioning #version	4.2.2 (13 May 2021)