Liquibase Bug triggered in the Upgrade of Spring Boot

[psavva]

Dear Support Team,

In liquibase Version 4.14.0, a bug was introduced:
liquibase/liquibase#3205

This bug now suffices in our application due to the upgrade, and the fact that our schemas use hypers "-" within the schema name.
Please review the workarounds available for this, and implement it in our implementation as to bypass this issue (until the liquibase bug is fixed and we upgrade spring boot again)

Cyprus

[psavva]

Please note that we implemented this workaround:

/**
 * The Application class.
 */
@SpringBootApplication
@EnableConfigurationProperties(DgcConfigProperties.class)
public class DgcVerifierServiceApplication extends SpringBootServletInitializer {

    /**
     * The main Method.
     *
     * @param args the args for the main method
     */
    public static void main(String[] args) {
        System.setProperty(GlobalConfiguration.PRESERVE_SCHEMA_CASE.getKey(), "true");
        SpringApplication.run(DgcVerifierServiceApplication.class, args);
    }
}