Upgrade to Hibernate 6 #31663
Closed
Upgrade to Hibernate 6 #31663
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
Also fix Reactor Netty HTTP to 1.1 M2 as the Data update seems to leak snapshots of the former into the build effectively breaking it as the Reactor snapshots introduce deprecations Boot compiles against.
Upgraded Hibernate artifact coordinates and version to Hibernate 6. A couple of previously referred to modules are not available in H6 anymore. They likely need review. Removed unsupported properties (AvailableSettings.USE_NEW_ID_GENERATOR_MAPPINGS has been removed entirely) from the configurable properties (deprecate in 2.7.x?).
spring-projects-issues
added
the
status: waiting-for-triage
|
Whoops. I forgot that we had a PR for the changes. They've been committed on |
wilkinsona
added
status: superseded
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.
Initial draft of a Hibernate 6 upgrade for Spring Boot. The first commit upgrades to Spring Data JPA and Envers versions that use Hibernate 6 already. This commit can be removed from the PR once spring-projects/spring-data-jpa#2423 is merged. We didn't merge that yet, as it is likely to break Boot unless it also upgrades to H6.
The upgrade removes support for the
USE_NEW_ID_GENERATOR_MAPPINGSsettings as H6 had that removed, unfortunately without prior deprecation in 5.6. Does it make sense to deprecate the Boot setting triggering that setting in its 2.7 branch then?I also had to adapt the sequence definitions for Liquibase and Flyway, as the names H6 expects are different (entity specific) now.