I’m converting an existing set of changeset files over to use liquibase 3.0.2 from version 2.0.0. I’ve updated the schema versions, but when running one of my changesets now, I’m receiving the following NPE:
DEBUG 7/23/13 3:18 PM:liquibase: Executing UPDATE database command: UPDATE ntdm.databasechangelogloc
k SET LOCKED = FALSE, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE ID = 1
INFO 7/23/13 3:18 PM:liquibase: Successfully released change log lock
Liquibase update Failed: Unknown Reason
SEVERE 7/23/13 3:18 PM:liquibase: Unknown Reason
The lock is released correctly in the databasechangeloglock table. This is on Postgres 9.2. All changesets previously ran correctly under 2.0 (no changes to content, except for the schema version).
When this error occurs, the errorlevel return value is not set correctly (running in a windows batch file environment)
**Also, version 2.0 logged the name of each changeset file as it was executed. We used those log messages extensively to track where we were when an update failed. I’ve tried both INFO and DEBUG levels with 3.0.2, but it doesn’t seem to log the change file it’s executing. That info would be nice to know in this situation. Could that message be added back?