Search Gradle plugins
| Plugin | Latest Version |
|---|---|
org.gradle.samplesPlugin required for authoring new Gradle Samples |
0.23
(26 January 2024) |
io.openapiprocessor.openapi-processorplugin to run openapi-processor-*, e.g. openapi-processor-spring (requires gradle 5.5+) |
2023.2
(19 December 2023) |
com.kazurayam.inspectus4katalonadds 'gradle drivers' task which downloads required jars from the Maven Central repository to locate them into the Drivers folder of a Katalon Studio project |
0.5.4
(10 December 2023) |
com.shinami.codeartifact-loginManages AWS CodeArtifact login tokens and integrates with Gradle's maven repositories. Running the login task requires AWS CLI v2 to be available and authenticated. |
0.1.1
(28 March 2023) |
com.needhamsoftware.unojarSingle jar packaging based on a JarClassLoader. Unlike maven shade and gradle shadow, this form of packaging does not intermix classes into a single directory, and thereby maintains a degree of separation between libraries with distinct licensing concerns. Does not require write access to the filesystem like capsule |
1.1.0
(20 January 2023) |
se.premex.ownershipCheck for existance of OWNERSHIP.toml in subprojects and verify that it contains ownership information. Will soon also check for description and have additional tasks to generate code owner files that are understood by source control systems. Attaches to the check |
0.0.11
(02 December 2022) |
io.qameta.allure-downloadAdds a task to download the required Allure version |
2.11.2
(25 October 2022) |
io.github.gunpowderGunpowderPlugin imports and configures the required dependencies to develop for Gunpowder. |
1.0.7
(19 July 2022) |
org.opendevstack.gradle.conventionsThis Gradle plugin sets basic OpenDevStack conventions when applied to a project, thus making the gradle project compatible to the build requirements. |
0.0.1
(08 July 2022) |
ch.essmann.gradle.check-java-versionThis plugin checks the Java version your Gradle build is running with. If the version is lower than the required minimum version or it exceeds the maximum version accepted, then the build is aborted with an friendly, easy to spot error message pointing towards the problem. This should help to avoid having to dig through the build output to find only to find an unsupported class file version error messages buried somehere in the output due to a bad Java runtime version. |
1
(03 July 2022) |