Search Gradle plugins

Plugin Latest Version

com.github.pdebicki.salted-component

A Gradle plugin for reading Maven's release.properties in Salt build system

1.1
(28 September 2018)

com.trevjonez.android-components

Variant aware android publishing, via `maven-publish` plugin.

0.1.0
(07 September 2018)

com.srcclr.gradle

The SourceClear Gradle Plugin keeps your Gradle projects free from vulnerable components

3.1.10
(18 August 2021)

io.alcide.gradle-semantic-build-versioning

This 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.github.turansky.kfc.webcomponent

Web component adapter for Kotlin/JS

2.15.0
(05 March 2021)

com.intershop.gradle.sonarQube

Gradle plugin to analyze Intershop Components with SonarQube

2.1.1
(21 October 2019)

com.github.kazurayam.visualtestinginks

With this Gradle Plugin you can import the components (Test Cases, Test Suites, Test Listener, Keywords) into your own Katalon Studio project and make it capable of running WebUI screenshot comparison testings.

0.1.21
(12 June 2019)

com.component.yz.depends.easy

depends for component

1.3
(08 May 2019)

com.intershop.gradle.component.installation

Gradle deployment plugins

1.0.0-dev.6
(31 August 2018)

javamuc.gradle-semantic-build-versioning

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