I’m having a look at the Liquibase product at the mo, mainly to help automate the database migrations for one of our clients. Currently the process is a bit hairy and manual. It’s easy to make mistakes and you have to be on the ball, plus rollbacks are awkard and generally it’s a mess.
Liquibase is a Database Change Management system - as they say “You never develop code without version control, why do you develop your database without it?” - and I agree.
However, in classic Open Source fashion, the documentation leaves something to be desired. So when I found myself trusting the documentation and getting the error:
when it was specified in both properties and as a parameter I should have realised that it was the documentation which was wrong, not me. I’m far too trusting….
So, when you set up the maven plugin in and they recommend doing this:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
you just ignore them as the configuration is only set for that particular phase - whereas you want the configuration for all phases.. so you should set it up like this instead, makes a lot of sense really.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21