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
Hi @rPraml , I have the thought that we can move away from classpath scanning for SQL DB migrations. So if we do that we could really change the way JdbcMigrations are found / loaded - change to using ServiceLoader instead.
Probably something like:
Add a new interface like JdbcMigrationFactory which has a method that creates JdbcMigration instances given a MigrationConfig
Use ServiceLoader to load the JdbcMigrationFactory(s) ... most people would probably create one factory
Ideally look to improve the JdbcMigration API such that we can provide an Ebean Database and Transaction such that the migration implementations can use the Ebean API more easily
I have a couple of things that are higher priority for me at the moment so this isn't an immediate thing plus we should look to make this change and still support the existing JdbcMigration mechanism.
Cheers, Rob.
The text was updated successfully, but these errors were encountered:
Hi @rPraml , I have the thought that we can move away from classpath scanning for SQL DB migrations. So if we do that we could really change the way JdbcMigrations are found / loaded - change to using ServiceLoader instead.
Probably something like:
I have a couple of things that are higher priority for me at the moment so this isn't an immediate thing plus we should look to make this change and still support the existing JdbcMigration mechanism.
Cheers, Rob.
The text was updated successfully, but these errors were encountered: