general core-plugin support

[meltzow]

Hi,
Assumption: you have a core plugin (used in multiple apps) and the grails-apps.
If you change a domain class in core, all apps need a separate migration. why it not possible to link the changelog-core.groovy (in core plugin) in all grails-apps. now we can create migrations just for the core domain classes, which is automatically done in all apps?

[jameskleeh]

@meltzow Are you asking for a new feature where changelogs that exist in plugins would be included when migrations are ran in an application?

[snimavat]

This could work when using the inhouse plugins, but with third party plugins it would be risky to run migrations from them.

[jchharris]

I have the same usecase where I have a number of inhouse plugins that contribute domain objects. It is desirable for the migration code to be owned by the plugins and be maintained as part of their release cycle. From an application perspective I would like to control via config which plugins are checked for migrations and in which order they are run. By order, I just mean simply running all migrations from plugin A, then all from plugin B. By making it configurable which plugins are considered for migration contributions I think it removes the risk of unexpected contributions or outcomes from 3rd party plugins.

[jdaugherty]

May be related to grails/grails-database-migration#139

[jdaugherty]

grails/grails-data-hibernate5#981 will likely address this issue. Today we have a common grails plugin that several applications extend. Migrations exist in common and we use a jar based deployment. When starting any of those applications, it will run the migrations from the common plugin via the code in grails/grails-data-hibernate5#981