Trying to use liquibase with spring, using the <includeAll> directive in a changelog that itself was included using an <include>. It properly finds the classpath resources in the given location, but then when it tries to actually resolve/open them, it improperly prefixes them with WEB-INF/classes – this causes problems, since the liquibase code is looking them up as classpath location, not a file path location.
It seems like some kind of mismatch between the spring resource loader returning file path vs the changelog code expecting a classpath location. Or maybe some other related impedance mismatch along the way. Not quite sure.
If that is not enough information, I can try to put together a unit test or integration test or example project.
MacOS/Linux, Java 6/7