file path in databasechangelog is absoulte since liquibase 3.2.0 when using includeAll inside a jar
Description
Environment
Liquibase 3.2.0 starting via commandline
Scripts inside jar file
Activity
Show:
Nathan Voxland July 10, 2014 at 9:15 PM
Fixed for 3.2.1
We have packaged all our scripts in a jar file under liquibase/scripts.
We do have a master.xml under liquibase:
In the databasechangelog-table the scripts are mentioned as e.g.
liquibase/master.xml
liquibase/scripts/instance.xml
We start liquibase via commandline giving the jdbc-driver and the scripts.jar as classpath:
when we tried to use 3.2.0 it fails because it tries to reexecute all changesets as the path-names of the files has been changed:
notice the "/tmp/liquibase-unzip8149400367604685392.dir" when accessing the first included file
when we try it with 3.1.0 it works as expected:
(the warning about the old scheme is ok - notice the used path)
This would break all existing scripts so we are not able to use 3.2.0 actually.