Search Gradle plugins
Plugin | Latest Version |
---|---|
io.github.jhvictor4.dockerbasic docker build & publishing plugin |
1.0.0
(31 December 2021) |
ch.addere.dga.connectorpluginThe Dependency Graph Analyser (DGA) Connector Plugin is designed for use with Gradle multi-project builds. It collects module dependency data from all Gradle projects within the build and exports this information in a format compatible with the DGA CLI tool for further analysis and visualisation. The plugin is typically applied using a Gradle init script, making it easy to integrate into existing builds without modifying individual project configurations. |
0.1.5
(13 September 2024) |
de.richsource.gradle.plugins.typescriptThis plugin makes it easy to build TypeScript projects using Gradle. Among other things, the plugin provides a task to run the TypeScript compiler. |
1.8.0
(20 March 2016) |
javamuc.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.1.1
(26 July 2018) |
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) |
com.osacky.taggerAn easy way to tag build scans for Gradle plugin authors. |
0.2
(03 August 2021) |
com.macwatters.elements-gradleElements is a framework for Java applications that allows configuration of Atoms (java classes, or groups of classes) using Groovy. See more at https://github.com/futehkao/elements. This plugin adds gradle tasks to run various provisions as well as launch scripts to applications built using the application plugin. It also facilitates copying groovy files from the conf directory into various locations, simplifying a lot of the common elements build tasks into an easy to read DSL. |
0.2.13
(04 September 2019) |
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) |
io.hkhc.simplepublisherWrapping build script for major repositories and make simple things as simple as possible |
0.4.1
(13 May 2020) |
eu.davidea.grabverAn easy Gradle plugin that follows semver.org rules to automatically generate the Patch version, Build number and Code version, while Major, Minor and Pre-Release suffix remain under our control. |
2.0.3
(01 August 2024) |