Search Gradle plugins

Flyway 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

• #deployment
• #continuousdelivery
• #continuousdeployment
• #flyway
• #database migrations
• #schema evolution
• #devops

Flyway 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

• #deployment
• #continuousdelivery
• #continuousdeployment
• #flyway
• #database migrations
• #schema evolution
• #devops

Provides core functionality for Javascript development, but does not apply conventions

• #node
• #nodejs
• #npm
• #javascript

Extends com.stano.base for multi-module application builds. Applies the base and jacoco plugins to the root project. Automatically derives project.version from git metadata: '<commitTimestamp>-<commitHash>' (or '<commitTimestamp>-<commitHash>-<buildNumber>' in CI). Inherits the 'root' BaseExtension and the jacocoRootReport aggregate coverage task.

• #convention
• #application
• #jacoco

android compose config for build.gradle, necessary related settings for compose will be automatically set

• #compose
• #config
• #android
• #convention

Orchestre le cycle de régénération JHipster (clean/generate/sync) sans perdre le code métier Kotlin persisté dans __codebase__/. Résolution par convention — aucune extension DSL requise.

• #jhipster
• #kotlin
• #codegen
• #persistence

Settings-plugin that applies the Foojay toolchain resolver so requested JDK versions auto-provision without Gradle's no-toolchain-repositories deprecation warning.

• #settings
• #toolchain
• #foojay
• #conventions

Extends com.stano.base for multi-module library builds. Applies the base and jacoco plugins to the root project. Does not set a project version — intended for library repositories that manage versioning separately. Inherits the 'root' BaseExtension and the jacocoRootReport aggregate coverage task.

• #convention
• #library
• #jacoco

A plugin that helps to maintain a semantic versioning of the build artifacts based on the project's git repository. It uses the current branch and the latest tag to enforce naming conventions

• #versioning
• #semantic
• #git

Adds Spex core and the spex JUnit Platform engine to the consuming project's test suite, configured against JUnit Jupiter. Requires that the consumer has applied a JVM plugin (java-library, java, or application) first.

• #spex
• #testing
• #junit
• #junit-platform
• #test-engine