Search Gradle plugins
Plugin | Latest Version |
---|---|
com.gmaslowski.gradle.plugin.propertyProperty Gradle Plugin |
0.4
(22 February 2016) |
com.netflix.nebula.info-jar-propertiesGradle plugin collect and provide information about the environment |
13.3.0
(08 October 2024) |
de.macnix.gradle.git-version-propertiesA plugin providing automatic versioning of CI/CD builds based on git tags and build info |
1.2.1
(23 July 2024) |
com.gorylenko.gradle-git-propertiesProduce git.properties for spring-boot-actuator |
2.4.2
(27 April 2024) |
com.neva.fork.propsExtension to Fork Plugin for reading encrypted properties like passwords. |
7.0.11
(02 August 2022) |
net.saliman.propertiesA Gradle plugin for loading and working with properties, enhancing Gradle's built in functionality. |
1.5.2
(16 February 2022) |
com.pswidersk.yaml-secrets-pluginGradle plugin to load secret properties from Yaml files. |
1.1.0
(22 September 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) |
com.github.jazzschmidt.properties-template-pluginValidates project properties against a template file to ensure required ones are present |
1.1.0
(26 January 2021) |
io.heapy.gradle.propertiesThis plugin used to override gradle.properties with local.properties for development purposes. As well as externalize version to build.properties file, to keep gradle.properties clean. |
1.1.2
(18 September 2020) |