3.5.3 version : includeAll uses Absolute Path as changeset path
Description
Environment
3.5.3, x86_64 x86_64 x86_64 GNU/Linux
Activity
Show:
Former user January 18, 2017 at 7:41 AM
I think this is related to https://liquibase.jira.com/browse/CORE-2851#icft=CORE-2851 and as I mentioned there I think this is the same as described here: http://stackoverflow.com/q/41678616/4864870
Maybe the technical information there could help to find and solve this issue.
Details
Details
Reporter
gourish singbal
gourish singbalComponents
Affects versions
Priority
MajorCreated January 6, 2017 at 1:30 PM
Updated January 18, 2017 at 7:41 AM
we are facing an issue where the databaseChangeLogMaster_REG.xml is as below but the objects created is with absolute path in databasechangelog table in db. example: /oravl01/oracle/liquibase_scripts/sql/relativetest/test4.sql
<?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>
command run is:
java -jar /oravl01/oracle/liquibase/liquibase.jar --changeLogFile=/oravl01/oracle/liquibase_scripts/databaseChangeLogMaster_REG.xml --driver=oracle.jdbc.OracleDriver --classpath=/oravl01/oracle/11.2.0.3/jdbc/lib/ojdbc6.jar --url=jdbc:oracle:thin:@10.232.230.35:1521
B --username=DBUSER --password=DBPASS --contexts=ENV --defaultSchemaName=DBUSER --logLevel=debug update
please check saw that there was a similar bug but it looks like it is not solved in 3.5.3
https://liquibase.jira.com/browse/CORE-2761#icft=CORE-2761 - 3.5.1: includeAll from the command line uses the absolute path as the changeSet path