We call liquibase programmatically and it works ok when the application runs standalone. When we run it inside jBoss however we get a ‘no parser found for changelog.xml’. In the find method around line 119 in DefaultPackageScanClassResolver I see that it checks for the FILE and JAR protocol, but we are having a jBoss module class loader which has the ‘vfs’ protocol.
Does that mean we need to upgrade to using liquibase 3.0.2 or is there some other way around this?
Mmm I upgraded to 3.0.2 and now getting an exception reported at https://liquibase.jira.com/browse/CORE-1325 that causes my war deployment to roll back.
-
Learn
-
Resources
-
Free Tools
OSS Risk Scanner Database DevOps Risk AssessmentCheat Sheets
Snowflake + Liquibase Databricks + Liquibase -
eBooks
6 Liquibase Community Risks & How to Avoid Guide: SOC 2 Compliance at the Database Layer Guide: Quantify the Value of Liquibase Secure -
Comparison Guides
Liquibase vs. Flyway Liquibase vs. Bytebase Liquibase Community vs Liquibase Secure
-
- Quickstart
- Get Started
- Documentation
- University
-
Resources
- Connect
- Contribute
- Join
- Blog