You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to liquibase-core bug CORE-1987, I am using liquibase maven plugin 3.0.6 and liquibase-hibernate 3.0, because is the only combination that makes liquibase:diff work.
But I realized that even when hibernate mappings and database are synced, liquibase:diff is producing always the same changesets, as if data base was empty.
¿Is this a bug of the older versions I am using? I can't check it out against liquibase maven 3.2.2 and liquibase-hibernate 3.4, because it always produces void changesets.
The text was updated successfully, but these errors were encountered:
Thanks to m50d (see #53 comments) my project is working with liquibase 3.3.0-SNAPSHOT and liquibase-hibernate 3.4 With this configuration liquibase:diff is not repeating changeSets, it works really nice!
Due to liquibase-core bug CORE-1987, I am using liquibase maven plugin 3.0.6 and liquibase-hibernate 3.0, because is the only combination that makes liquibase:diff work.
But I realized that even when hibernate mappings and database are synced, liquibase:diff is producing always the same changesets, as if data base was empty.
¿Is this a bug of the older versions I am using? I can't check it out against liquibase maven 3.2.2 and liquibase-hibernate 3.4, because it always produces void changesets.
The text was updated successfully, but these errors were encountered: