Upgrade 2.0.5 => 3.1.1

2.0.5 -> 3.1.1 should be backwards compatible with the change logs and you should just have to update your jar file. 

http://www.liquibase.org/v3_upgrade.html and http://www.liquibase.org/v3_1_upgrade.html should give more details on some edge cases.


What is involved in upgrading Liquibase 2.0.5 to 3.1.1? Specifically, do any of the changelogs need to be changed or it’s just a matter of replacing the JAR and updating configuration files?


Upgrade was no problem except the fact that all changesets with in it will not run on both Windows und Linux at the same time (before running clearCheckSums).

I have no idea why because with versions prior to 3.x it worked really great (and nothing was changed on the old 2012er changesets).

Any hint?


There may be some checksum differences between 2.x and 3.x due to checksum algorithm changes. It should be consistant between linux and windows, though. 

You say that with 3.x you are seeing problems where linux and windows generate different checksums for the same commands?

Are you using any utf8 style chars in the sql tags?