Fix examples in Metadata Format documentation chapter - #51097
Merged
Conversation
spring-projects-issues
added
the
status: waiting-for-triage
snicoll
added
type: documentation
See spring-projectsgh-51097 Signed-off-by: Stefano Cordio <stefano.cordio@gmail.com>
snicoll
force-pushed
the
fix-metadata-example
branch
from
July 23, 2026 10:09
70b12bf to
834f7e7
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The examples related to Hibernate properties in the Metadata Format chapter were still referring to
JpaPropertiesfrom Boot < 2.1, which had a nestedHibernateclass.This PR aligns the package names to version 4 and replaces the
spring.jpa.hibernategroup example withspring.jpa.hibernate.naming(the closest I could find, but let me know if you prefer something else there).The same issue is also in older documentation before version 4, like 3.3, but the fix would be slightly different due to the package names. Happy to raise a separate PR for that, or you might find it easier to backport and update the fix on your own, just let me know 🙂