I seem to run into problems with HSQLDB where liquibase gets stuck at "Waiting for lock..." I haven't attempted to debug it, but being that I'm running HSQLDB as an in memory database, there obviously shouldn't be an contention on the change lock.
How is the lock released? If I kill liquibase while its in the middle of doing something, will it leave the lock in place? The problem I have is that in my development setup I'm running liquibase each time my application starts up. So liquibase always runs on startup even if there is no migration that is need. So its likely I may kill the application while liquibase is in the middle of doing something (really nothing).
Darren
How is the lock released? If I kill liquibase while its in the middle of doing something, will it leave the lock in place? The problem I have is that in my development setup I'm running liquibase each time my application starts up. So liquibase always runs on startup even if there is no migration that is need. So its likely I may kill the application while liquibase is in the middle of doing something (really nothing).
Darren