Search Gradle plugins
| Plugin | Latest Version |
|---|---|
nl.leeuwit.gradle.jpmsA Gradle plugin that adds useful tasks to support the Java Platform Module System |
0.0.8
(17 August 2021) |
com.bmuschko.tomcatGradle plugin supporting deployment of your web application to an embedded Tomcat web container. |
2.7.0
(29 June 2021) |
com.bmuschko.tomcat-baseGradle plugin supporting deployment of your web application to an embedded Tomcat web container. |
2.7.0
(29 June 2021) |
com.github.ayltai.spring-graalvm-native-pluginSupport for building Spring Boot applications as GraalVM native images |
1.4.10
(15 June 2021) |
com.ainrif.apiatorProvides Apiator support during gradle build |
0.15.0
(14 June 2021) |
com.optum.giraffleProvides dsl and support for connection to Tigergraph servers, and executing scripts against Tigergraph. |
1.3.5
(11 June 2021) |
com.airsaid.incrementlintA Gradle Plugin that supports Lint increment scanning. |
1.0.0
(27 May 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) |
de.timfreiheit.resourceplaceholdersGradle plugin which adds support for ${placeholder} manifestPlaceholders in Android resource files |
0.4
(10 May 2021) |
com.bmuschko.izpackGradle plugin that provides support for packaging applications for the Java platform via IzPack. |
3.2
(29 April 2021) |