Jmix Studio for now has two approaches for generating Liquibase scripts in composite project.
The first one - generation in composite project.
Liquibase scripts generated for the the subproject (module) itself and all dependent modules of this composite project. So you have datastore defined only in your main application and all Liquibase scripts are generated for this datastore. Add-ons doesn’t provide any script in this case and you don’t need to have database for each add-on.
The second one - generation for each sub-project separately. You need to open each add-on as a separate project in IDE, create datastore and generate Liquibase changelogs for this datastore. Then this scripts provided for add-ons and application(s) that depends on this add-on. To keep scripts up to date you need to have database set up for each add-on and generate scripts for add-on data model updates.
Thanks for your feedback.
We will think about ability to generate scripts only for specific add-on (without dependencies) with no need to open it as a diffrent IDE project.
In the Jmix 1.4 and 1.5 projects with flow UI, the original method was working fine.
However, after upgrading to Jmix 2.0, it no longer functions in the same way.
I will reconsider your suggestions, and I kindly ask the Jmix team to explore the possibility of correcting it to restore its original behavior.