Build scripts: check database upgrade before deploy

[php-coder]

[php-coder]

After updating password in src/main/resources/liquibase/liquibase.properties, creating SSH tunnel (ssh -L 3306:localhost:3306 my-stamps.ru) and run mvn liquibase:status I got the following error:

59 change sets have not been applied to mystamps@localhost@jdbc:mysql://localhost:3306/mystamps
     /Users/coder/git/mystamps.git/src/main/resources/liquibase/initial-state.xml::create-users_activation-table::php-coder
     /Users/coder/git/mystamps.git/src/main/resources/liquibase/initial-state.xml::create-users_table::php-coder
...

It turns out that the path to the migration is also very important. When we run migration during application startup we have prefix classpath:/ (example: classpath:/liquibase/version/0.4/2016-02-19--csrf_events.xml). When I run it locally it has prefix /Users/coder/git/mystamps.git/src/main/resources/ (example: /Users/coder/git/mystamps.git/src/main/resources/liquibase/version/0.4/2016-02-19--csrf_events.xml). Looks like we should unify changeLogFile parameter in liquibase-maven-plugin with liquibase.change-log from application-prod.properties.

[php-coder]

We should only modify changeLogFile parameter in liquibase-maven-plugin because classpath: prefix will be ignored (since 3.0.6 version). See for details: http://stackoverflow.com/questions/16605099/using-liquibase-file-paths-via-both-maven-and-spring

[php-coder]

Command for checking for updates should be mvn liquibase:status -Dliquibase.password=xxx