Fix ConcurrentModificationException when running dbm-gorm-diff #57
Conversation
This file contains 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
This fix upgrades liquibase-core to version 3.4.2, this has been identified as a workaround solution to the concurrent modification exception being thrown by gorm-diff, generate-changelog etc. Some parts of the api in liquibase changed between 3.3 and 3.4, so while the original error went away, bringing in 3.4.2 broken the dbmUpdate functionality. This commit fixes this issue with also and no workarounds should be needed. #47
rvanderwerf
added a commit
that referenced
this pull request
Mar 16, 2016
Fix ConcurrentModificationException when running dbm-gorm-diff
rvanderwerf
added a commit
that referenced
this pull request
Mar 17, 2016
rvanderwerf
added a commit
that referenced
this pull request
Mar 18, 2016
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.
This fix upgrades liquibase-core to version 3.4.2, this has been identified as a
workaround solution to the concurrent modification exception being thrown by
gorm-diff, generate-changelog etc.
Some parts of the api in liquibase changed between 3.3 and 3.4, so while the
original error went away, bringing in 3.4.2 broken the dbmUpdate
functionality. This commit fixes this issue with also and no workarounds
should be needed.
This fixes #47