Liquibase Jmix 2.8

Support
#1

I have migrated all my Jmix add-ons from version 2.7 to version 2.8.

The build fails at the Liquibase stage due to duplicate identifiers.
It seems that all the inclusions (for example: <include file="/io/jmix/securitydata/liquibase/changelog.xml"/>) that I had in the changelog.xml file of each add-on are now detected automatically.
So I removed all dependency inclusions and the application started up.

But I can’t run the tests in each addons!
Do I need to create a ‘test’ changelog.xml file with the dependencies, or can I run the automatic Liquibase 2.8 from my JUnit and Cucumber tests?

#3

Hello Benoît!

Typically, the main changelog.xml contains only the scripts related to that specific add-on, in order to avoid duplication when its changelog is included in another changelog.
If running the test environment requires more scripts than are listed in the main changelog.xml, they are included in the test changelog.xml. You can see that Studio creates a separate test changelog.xml by default when you create a new “addon” project.

Regards,
Dmitry