$ the-wire · showcase
Spring Data moves to JSqlParser 5.4 and Hibernate 7.4.8.Final
By RepoJournal · Filed · About Spring · Composed from the cited sources · methodology
3 people shipped this
A dependency train through spring-data-jpa lands JSqlParser 5.4, whose removed constant forced a code change in Spring Data's query enhancer, while the build module holds Surefire back to keep Develocity working.
Adapt JSqlParserQueryEnhancer to changes in JSqlParser 5.4. spring-projects/spring-data-jpa
JSqlParser 5.4 dropped CCJSqlParserUtil.ALLOWED_NESTING_DEPTH, so JSqlParserQueryEnhancer now reads the value through Feature.allowedNestingDepth. If you subclass or reference that enhancer directly, this is the compatibility point to check before taking 5.4.
Downgrade to Surefire 3.5.6. spring-projects/spring-data-build
The build moved back to Surefire 3.5.6 after the Develocity plugin failed against newer Surefire versions. Anyone mirroring spring-data-build's plugin config should stay on 3.5.6 rather than following the 3.6.0 plugin bump in the same batch.
Upgrade to Hibernate 7.4.8.Final. spring-projects/spring-data-jpa
Hibernate 7.4.8.Final is now the version spring-data-jpa builds against, and spring-data-rest followed with the same upgrade, which keeps the two modules aligned on one Hibernate line.
Upgrade plugins. spring-projects/spring-data-build
Roughly a dozen build plugins came forward at once: Maven Compiler 3.16.0, Deploy 3.2.0, Build Helper 3.6.2, Exec 3.6.4, Failsafe 3.6.0, Surefire 3.6.0 and setup-java v6.0.1. JUnit moved to 6.1.3 and setup-java now pins a verbatim Java version to avoid variable expansion.
Attempt to add tags to antora config spring-projects/spring-grpc
Quieter desks: spring-grpc attempted Antora tags in its docs config, and spring-data-bom ran a routine dependency refresh.
