Search Gradle plugins
| Plugin | Latest Version |
|---|---|
nebula.debGradle plugin for constructing linux packages, specifically RPM and DEBs. |
9.1.1
(01 February 2022) |
org.s7s.build.instanceApplies configuration specific to Sandpolis instance modules |
0.1
(21 December 2021) |
me.julb.gradleplugins.aggregatespringdocopenapidocsCopies the OpenApi specifications generated by SpringDoc of all the subprojects into one target folder. |
1.0.8
(08 December 2021) |
com.sandpolis.build.instanceThis plugin applies configuration specific to Sandpolis instance modules |
0.3
(28 November 2021) |
io.github.david99999.gradle.notifierThis plugins provides a convenient way for performing tasks after specific gradle tasks finishes or fails |
0.0.1
(22 October 2021) |
com.twilio.guardrailPrincipled code generation from OpenAPI specifications |
0.64.3
(06 July 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.michaelruocco.rest-pollingGradle plugin that enables polling of rest endpoints for a specific result |
0.1.1
(26 March 2021) |
com.athaydes.sdkmanA Gradle Plugin that enforces a specific SDKMAN! JVM is used by Gradle |
1.0-RC3
(24 October 2020) |
org.flywaydb.pro.flywayFlyway by Redgate is an open-source database migration tool. It strongly favors simplicity and convention over configuration. It is simple, focused and powerful. It runs on Windows, Mac OSX and Linux, Java and Android. It is based around just 6 basic commands: Migrate, Clean, Info, Validate, Baseline and Repair. Migrations can be written in SQL (database-specific syntax (such as PL/SQL, T-SQL, ...) is supported) or Java (for advanced data transformations or dealing with LOBs). It has a Command-line client. If you are on the JVM, we recommend using the Java API (also works on Android) for migrating the database on application startup. Alternatively, you can also use the Maven plugin, Gradle plugin, SBT plugin or the Ant tasks. And if that not enough, there are plugins available for Spring Boot, Dropwizard, Grails, Play, Griffon, Grunt, Ninja and more! Supported databases are Oracle, SQL Server, SQL Azure, DB2, DB2 z/OS, MySQL (including Amazon RDS), MariaDB, Google Cloud SQL, PostgreSQL (including Amazon RDS and Heroku), Redshift, Vertica, H2, Hsql Derby, SQLite and solidDB. More info: https://flywaydb.org |
7.0.0-beta1
(02 September 2020) |