Well at least I now don’t need to worry about any of the dev’s moving/renaming a db-changelog file.
I’m using the logicalFilePath on every file and now and I find that if it’s run it from the wrong directory I get an error.
bla:~$ liquibase --username=bla --password=bla --url=jdbc:postgresql://127.0.0.1/bla --changeLogFile=“DB-bla-test/database/db-changelog-bla.xml” update
Liquibase Home: /home/bla/liquibase
INFO 12/12/11 17:32:liquibase: Successfully acquired change log lock
SEVERE 12/12/11 17:32:liquibase: Error thrown as a SAXException: -Unable to read file
liquibase.exception.SetupException: -Unable to read file
at liquibase.change.core.SQLFileChange.loadFromFileSystem(SQLFileChange.java:128)
at liquibase.change.core.SQLFileChange.init(SQLFileChange.java:83)
at liquibase.parser.core.xml.XMLChangeLogSAXHandler.startElement(XMLChangeLogSAXHandler.java:352)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
But this is fine as it stops any execution, in my case at least.
I would have thought there would be a config option for this somewhere. I’m sure that a lot of people don’t want that dependency on the file name. Renaming a file seems like a likely proposition to me.
Are there any plans to remove this dependency on the file name?
Thanks for the help.
David.