mybatis-migrations-3.3.11

Two bug fixes:

• Error message was not helpful when the changelog table was missing. #220
• When the directory specified by --path does not exist, 'init' command did not create the directory as documented. #225

mybatis-migrations-3.3.10

List of user visible changes:

• Add 'redo' command. #205
• Add hooks for the 'script' command. #203
• Possible syntax error when using -- //@DELIMITER in a script. #182

mybatis-migrations-3.3.9

Bug fix:

• Driver JAR in the lib directory is not correctly picked up. #176

mybatis-migrations-3.3.8

• Removed -XX:PermSize=128m JVM option when executing migrate command.

mybatis-migrations-3.3.7

Bug fix:

• version command fails when there is no changelog table. #160

There should be no backward incompatible change since 3.3.6.

mybatis-migrations-3.3.6

Enhancements:

• It is now possible to define environment settings using Java System Properties or Environment Variables. #114
• status command now shows locally-missing migrations. #145

Bug fixes:

• An error could be ignored when one of multiple statements in a script fails. #118

mybatis-migrations-3.3.5

Enhancements:

• bofore_new and after_new hooks. #106
• Print a warning when there is a skipped migration or a missing migration script. #125

Bug fixes:

• Possible ArrayIndexOutOfBoundsException when reading a script. #127
• 'script' command can generate incomplete script. #121

mybatis-migrations-3.3.4

The previous fix didn't replace variables correctly. #117

mybatis-migrations-3.3.3

Fixed a regression.

• Down command fails if you don't have have a line break at the end of the UNDO statement. #117

mybatis-migrations-3.3.2

Enhancements:

• Added '--quiet' command line option. #92
• Added '--color' command line option. #104
• It is now possible to specify multiple characters as a delimiter. #96
• Hooks are now applied to 'version' and 'pending' commands as well. #81
• Added a new environment option 'ignore_warnings'. #85
• Migrations can now use a custom FileMigrationsLoader. #107
• Reduced memory usage when reading a large migration script. #101

The default value of 'ignore_warnings' is 'true', so SQL warnings do not stop migration as they did in 3.3.1. See #85 for more info.