3.5.1: includeAll from the command line uses the absolute path as the changeSet path

Description

Using a changelog with something like: <includeAll path="com/example/seq"/> should track and store files as com/example/seq/seq1.xml and com/example/seq/seq2.xml but with 3.5.0 started trackign them as c:\path\to\com\example\seq\seq1.xml.

This caused them to re-execute because liquibase saw the path as different.

Environment

Command line and other uses of FileSystemResourceAccessor

Activity

Show:

Vincent Deygas February 15, 2017 at 2:23 PM

Reopened here: https://liquibase.jira.com/browse/CORE-2980
(as this one has been closed even if not fully fixed)

gourish singbal January 6, 2017 at 1:04 PM

This problem is still existing in version 3.5.3 as we are facing the same .
i.e in the databaseChangeLogMaster_REG.xml we have

<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.1.xsd">

<includeAll path="sql/relativetest" />

</databaseChangeLog>

but when i run the liquibase command:

java -jar /oravl01/oracle/liquibase/liquibase.jar --changeLogFile=/oravl01/oracle/erd_folder/payment/capm/databaseChangeLogMaster_REG.xml --driver=oracle.jdbc.OracleDriver --classpath=/oravl01/oracle/11.2.0.3/jdbc/lib/ojdbc6.jar --url=jdbc:oracle:thin:@HostIP:1521BNAME --username=DBUSERNAME --password=PASSWORD --contexts=ENV --defaultSchemaName=DBUSERNAME --logLevel=debug update

the databasechangelog table gets populated but with full path :
/oravl01/oracle/liquibase_scripts/sql/relativetest/test1.sql

someone please help with an update.

Nathan Voxland May 24, 2016 at 9:18 PM

Thanks for the update

Mateusz Jędraszkiewicz May 19, 2016 at 9:36 AM

Fixed

Nathan Voxland May 18, 2016 at 4:12 PM

Fixed in 3.5.2

Fixed

Details

Reporter

Fix versions

Affects versions

Priority

Created May 18, 2016 at 4:11 PM
Updated February 15, 2017 at 2:23 PM
Resolved May 18, 2016 at 4:12 PM