Search Gradle plugins

Want to include your Gradle plugin here?
Plugin Latest Version

com.softicar.gradle.selenium.grid

This plugin is useful for projects executing unit tests based on the Selenium (https://www.selenium.dev/) framework. See the Javadoc of the plugin class for more details.

 4.0.5
(06 February 2023)

com.softicar.gradle.code.validation

This plugin enables a project to execute self-contained code validation logic, i.e. code validation logic that is implemented in the project itself or in one of its dependencies.

 4.0.5
(06 February 2023)

com.needhamsoftware.unojar

Single 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)

io.datapith.cukedoctor

This plugin brings the ability to execute Cukedoctor during the gradle build.

 0.1.0
(22 December 2022)

com.github.psxpaul.execfork

Execute Java or shell processes in the background during a build

 0.2.2
(01 December 2022)

io.github.meiblorn.require-docker

Gradle plugin to require Docker to be up and running before executing attached tasks

 1.2.0
(30 November 2022)

de.qualersoft.jmeter

Plugin to execute JMeter tests.

 2.4.0
(24 July 2022)

pub.techfun.docker.plugin.java

This plugin use pure java client to execute docker command to complete common tasks like build docker image, push to local or remore registry, deploy to local or remote host

 0.0.8
(18 July 2022)

pub.techfun.docker.plugin.cmd

This plugin use local machine shell to execute docker command to complete common tasks like build docker image, push to local or remore registry, deploy to local or remote host

 0.0.8
(18 July 2022)

ch.essmann.gradle.check-java-version

This 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)
Previous Next