How to avoid circular references in Java Liquibase migration?
I have a SpringBoot application and Java Liquibase migration code that used to work, but now migrations can’t go through due to a circular dependency error.
Two liquibase instance on a spring app with different loading times
How can I set two liquibase instances on a single Spring app which one of them runs first before Spring context is initialized and the other one after context initialized.
Running Liquibase with Custom Change
Currently I’m experimenting with Liquibase and trying to run a customChange.
The Project is Spring-Webflux based, compiled into a fat jar.
Every time I try to run the Liquibase with the customChange I’ve created, I ran into