Depends on semantic between Liquibase and JPA are no longer applied with custom SpringLiquibase #18673
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…lled if user has registered `SpringLiquibase` bean. This commit fixes this issue by changing the import place. Closes spring-projectsgh-18666
spring-projects-issues
added
the
status: waiting-for-triage
wilkinsona
added
type: regression
snicoll
changed the title
LiquibaseEntityManagerFactoryDependsOnPostProcessor is no longer called
snicoll
pushed a commit
that referenced
this pull request
Oct 22, 2019
This commits restores the dependency between Liquibase and the JPA EntityManager even if a custom `SpringLiquibase` is configured. See gh-18673
snicoll
added a commit
that referenced
this pull request
Oct 22, 2019
|
Thanks again @nosan |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
LiquibaseEntityManagerFactoryDependsOnPostProcessoris no longer called if a user has registeredSpringLiquibasebean.This commit fixes this issue by changing the import place.
see gh-18666