Comments (2)
Thanks for responding, that's good to hear as I'm embarking on a journey where I will be hitching my company's data migration approach to Liquibase, and were not in a position to convert from Gradle to maven right now.
I have a specific question that might be a feature request, and I'll post that as a separate thread.
from liquibase-gradle-plugin.
This project (and the liquibase Groovy DSL) are both still maintained, though like many open source efforts, I can only work on it in my spare time.
The Gradle plugin in particular is designed to be a simple wrapper around the Liquibase CLI, so it doesn't generally require a lot of maintenance as long as that CLI remains stable, just the occasional patch to deal with java or Gradle changes.
One thing that I'd like to do, but haven't had time to, is improve the test suite for the plugin. I could merge code much quicker if I had a good way to make sure a change didn't break anything in older versions of Java/Gradle/Liquibase.
from liquibase-gradle-plugin.
Related Issues (20)
- Publish plugin version 2.2.0 HOT 7
- Liquibase is not using module directory as working directory. HOT 1
- Cannot pass more than one context with Gradle Plugin
- Cannot invoke method get() on null object
- Cannot fingerprint input property HOT 5
- Configuration as a dependency Gradle 8.0 HOT 2
- Problem with using the Liquibase block in build.gradle HOT 1
- Problem with labelFilter argument HOT 2
- Avoiding duplication of properties between spring boot and gradle HOT 1
- With Gradle 7.6.2 and Java 17, Liquibase build throwing 'org.liquibase.gradle.LiquibaseTask' property 'command' is missing an input or output annotation HOT 5
- Is there a simple way to disable the plugin? HOT 2
- liquibase-gradle-plugin should declare picocli as a transitive dependency HOT 9
- Generate Changelog with defaultSchemaName not possible HOT 3
- Running Liquibase 4 with Gradle 8 causes error could not find method getMain() for arguments [] HOT 2
- spring boot v3 integration example HOT 5
- micronaut 4 liquibase plugin integration
- Liquibase --username argument should be placed after the command HOT 1
- Task "updateSQL" ignores "--outputFile" parameter HOT 3
- Upgrade to "org.apache.groovy:groovy" HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from liquibase-gradle-plugin.