Closed RafiIsaharov closed 2 months ago
/cc @andrejpetras (liquibase), @geoand (liquibase), @gsmet (liquibase), @zakkak (native-image)
@gcw-it could you have a look at this one while you're at it? Maybe it's already fixed by your ongoing PRs?
@RafiIsaharov You're in luck. PR #41928 fixes your issue. I could reproduce your problem, and with the PR included your application started without problems and ran the Liquibase migrations successfully.
The answer to when the patch will be incorporated into a Quarkus release, will have to be given by @gsmet .
It should be part of the next 3.13 release
Yeah so not 3.13.0 but 3.13.1 released in two weeks.
@gcw-it thanks for checking!
Thanks again @gcw-it for this important fix!
@gsmet @geoand You're welcome!
I'm facing an issue with quarkus-liquibase, particularly with the XML Changelog. I noticed an issue on GitHub, which can be found at https://github.com/quarkusio/quarkus/issues/27437, opened in 2022.
Configuration:
files : https://github.com/RafiIsaharov/esb-infra/tree/main/src/main/resources/db/postgres
Snapshot of changelog-master.yml:
Snapshot of changelog.002.xml:
Error Trace: exception_liquibase_using_changelog_as_xml.txt
Observations:
This issue occurs only in the native image, not when running the runnable jar.
The application fails to start with this error.
Quarkus version: 3.12.3
Java version: 17.0.11+7-LTS, vendor version: Oracle GraalVM 17.0.11+7.1
Apache Maven 3.9.6
Current Workaround: To overcome the issue with the XML changelog file, I am converting it into an equivalent SQL file format.
Reproduce the issue: I've uploaded the code to my GitHub repository, which includes the docker-compose.yaml file for the Postgres database. You can download and replicate it from the main branch https://github.com/RafiIsaharov/esb-infra.git.