In our recent grails project, we were about to move to production so we decided to manage the database changes with liquibase. So we generated the changelog from development env by executing the command "grails generate-changelog /home/uday/projects/projectName/grails-app/migrations/changelog.xml" which contained all the table creation...
The current project I am working on, is going through QA. At the same time development of the new features and bug fixing is on and we couldn't afford to loose the test data. So synchronizing the state of the QA database with the development was becoming a pain. So we decided to use grails liquibase plugin. I found one great article by...