New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow default migration resolvers to be overriden #1078
Comments
A third proposal: provide an additional flag parameter (flyway.skipDefaultResolvers) to allow to skip the default resolvers. This would also be completly backward compatible. |
Introduces a new parameter flyway.skipDefaultResolvers and its corresponding property to skip usage of default built-in resolvers.
created a new PR base on my previous patch: |
Implementation of skipDefaultResolvers is merged with #1191. This allows to replace default resolvers, however custom subclasses of the resolvers are not yet supported. |
Thanks @pauxus for the PR! |
Current behavior:
Problem description:
When we want to override SpringJdbcMigrationResolver, we have no possibility to do that. Because SpringJdbcMigrationResolver is added to the resolvers by default and it is not possible to remove it. Spring JDBC migrations will be resolved twice (he first time from default resolver the second time from the default one) The usecase is not rare e.g.:
http://stackoverflow.com/questions/27105681/flyway-db-need-access-to-spring-environment-for-migration
#1062
Solution proposals:
The text was updated successfully, but these errors were encountered: