Allow default migration resolvers to be overriden #1078
Closed
Labels
Milestone
Comments
martin-grofcik
added a commit
to martin-grofcik/flyway
that referenced
this issue
Aug 11, 2015
martin-grofcik
added a commit
to martin-grofcik/flyway
that referenced
this issue
Aug 11, 2015
A third proposal: provide an additional flag parameter (flyway.skipDefaultResolvers) to allow to skip the default resolvers. This would also be completly backward compatible. |
pauxus
added a commit
to pauxus/flyway
that referenced
this issue
Jan 13, 2016
Introduces a new parameter flyway.skipDefaultResolvers and its corresponding property to skip usage of default built-in resolvers.
pauxus
added a commit
to pauxus/flyway
that referenced
this issue
Jan 15, 2016
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. |
axelfontaine
added a commit
to flyway/flywaydb.org
that referenced
this issue
Feb 3, 2016
Thanks @pauxus for the PR! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: