When running Spring boot 1.4.0 (liquibase 3.5.1), with following configuration :
The db.changelog-master.yaml contains an includeAll reference (relative to file location)
SpringBoot is ran not as standalone but as a Jar deployed from an existing Tomcat instance
we have following problem :
Liquibase complains the folder is empty / no file found.
Tracing down roughly shows that the system is comparing a start path like 'jar:file:[correct path to jar]![correct includeAll folder path]' to the path inside the jar, like includeAll folder path...
obviously, it cannot work...
A QUICK fix would be much appreciated as this is blocking our migration to SpringBoot 1.4.0 (SpringBoot 1.3.6, with liquibase 3.5.2 works with exactly the same configuration)
springboot 1.4.0, tomcat 7, java 8