I’m using Liquibase 2.0.1 in a Java Web Start application, by way of the SpringLiquibase integration. While snooping on my application’s http traffic using Fiddler, I noticed that the liquibase jar was being repeatedly retrieved 72 times. At almost 1MB each time, that’s a lot of overhead.
This behavior pretty much makes Liquibase unacceptable to use in my situation. Any thoughts on how to work around it? For example, is there a way to configure in advance what classes to use, to avoid the need for ServiceLocator to scan for them?