includeAll not working with Liquibase 4.0.0
See original GitHub issueStarting with Liquibase 4.0.0, the includeAll definition in a change log file doesn´t work anymore if the referenced files are placed in a JAR file. It´s working fine, if the files can be referenced from a target folder during development but not when the changesets should be accessed from JAR.
For details, see also https://forum.liquibase.org/t/includeall-with-v4-0-0/4655 Text from forum update With the Quarkus version 1.7.1 which uses Liquibase 3.9.x everything works fine.
But Quarkus 1.8.x upgrades to Liquibase 4.0.0 and this causes issues with change sets using the includeAll tag.
Our changeLog.xml contains following: <includeAll path="db/1.0.0/" errorIfMissingOrEmpty="true"/>
When we start the application in the Quarkus dev mode (mvn quarkus:dev) everything works fine; the changeLog is read and every file under the given path (db/1.0.0/) is executed/checked from Liquibase.
But if we run the application directly (with java -jar) we are getting following error:
Caused by: liquibase.exception.SetupException: Could not find directory or directory was empty for includeAll 'db/1.0.0/'
at liquibase.changelog.DatabaseChangeLog.includeAll(DatabaseChangeLog.java:528)
The resources under this given folder are just not found.
If I define the includes per file, it´s working fine:
How can we define the includeAll tags with the new Liquibase 4.0.0 version?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:7
- Comments:18 (6 by maintainers)
Top GitHub Comments
In testing #1665, we found that the specific error you were seeing was different than the error we had reproduced and fixed.
I was able to reproduce the reported
Could not find directory or directory was empty for includeAll
error with Liquibase 4.0.0 but it either went away or matched the error that was fixed in #1665 depending on my setup. So, I’m not sure if the original error is still around in 4.2.2 and I’m just not correctly reproducing it, or if the original issue was solved and you moved on to new problems.I’ll see if I can reproduce it using the steps in quarkusio/quarkus#14751 to better understand what is going on.
Hi @acierto Thanks for the feedback on this. Windows 2008 R2 is no longer supported. https://support.microsoft.com/en-us/help/4456235/end-of-support-for-windows-server-2008-and-windows-server-2008-r2 I’ll take a look at the JRE11.