Search Gradle plugins
| Plugin | Latest Version |
|---|---|
com.legyver.update-readme-versionUpdate the library version in your README files based on project version. In effect, this auto-updates the standard gradle dependency usage ONLY (not short form, or maven, or grape, etc) |
1.0.0
(18 June 2022) |
org.gatored.gatorgradleGradle plugin for integrating the auto-grading tool GatorGrader as a runnable, configurable task |
0.5.2
(25 April 2022) |
com.gradleup.auto.manifestAutomatically creates AndroidManifest.xml so you don't have to |
2.0
(16 April 2022) |
com.github.hanlyjiang.inline_apk_to_assetsPlugin for auto copy plugin's apk to host app assets dir |
0.0.14
(12 April 2022) |
com.louiscad.complete-kotlinEnable auto-completion and symbol resolution for all Kotlin/Native platforms. |
1.1.0
(10 January 2022) |
com.daofeng.auto-patch-pluginA flug-in to hotfix for android |
1.0.7
(05 November 2021) |
com.karmanno.plugins.semverPlugin for auto increase version |
2.0.0
(08 October 2021) |
com.airsaid.okmockOKMock is a Java mock tool, used to quickly auto-fill field data. |
1.0.3
(09 September 2021) |
com.ageet.apknameAuto naming for android apk |
0.4.0
(24 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) |