Hello,
I am using Liquibase for some time now. I use the library at runtime within my application to update the database when my application starts up.
Now I am working in a regulated environment, every Java dependency used by my application must be checked, documented and controlled throughout the lifecycle of my application. Therefore, it would be great if the Liquibase library itself would have as few dependencies as possible. I only use the basic functionality like xml-based change logs to update databases. Therefore, the yaml and opencsv dependencies are not used for my use-case. Also, the Liquibase library started to use several commons libraries. Some of them are only used because of one or two methods. This results in dependency creep.
Are there any plans to reduce the number of dependencies again? I think the commons libraries would be easy to remove as the few methods that are needed could be added as Utils classes in the Liquibase library itself. For the yaml and opencsv dependencies, these might need a bit more work.
Regards,
Michael