[WIP] DO NOT MERGE!!!! - Springboot 4.0.x upgrade #3221
Draft
nrknithin wants to merge 2 commits intoapache:mainfrom
Draft
[WIP] DO NOT MERGE!!!! - Springboot 4.0.x upgrade #3221nrknithin wants to merge 2 commits intoapache:mainfrom
nrknithin wants to merge 2 commits intoapache:mainfrom
Conversation
…stence module and update entity scanning imports
This was referenced Apr 28, 2026
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
1 participant
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.
Kie-Issue: apache/incubator-kie-issues#2288
Related PRs
Summary
Upgrade
optaplanner-spring-integration(autoconfigure + starter) from Spring Boot 3.5.12 to 4.0.5 and Spring Framework 6.2.17 to 7.0.6.What changed
build/optaplanner-build-parent/pom.xml3.5.12→4.0.56.2.17→7.0.61.5.25→1.5.32(matches SB 4.0.x line)spring-boot-persistenceto dependencyManagement (new module in SB 4.0; see entity-scan import migration below)optaplanner-spring-integration/optaplanner-spring-boot-autoconfigure/pom.xmlOptaPlannerAutoConfiguration.java
ChainedSpringTestConfiguration.java
GizmoSpringTestConfiguration.java
MultiModuleSpringTestConfiguration.java
NoConstraintsSpringTestConfiguration.java
org.springframework.boot.autoconfigure.domain.*→org.springframework.boot.persistence.autoconfigure.*.Why
Spring Boot 4.0 extracted persistence-related auto-configuration into a new spring-boot-persistence module and moved EntityScan/EntityScanPackages/EntityScanner to org.springframework.boot.persistence.autoconfigure. The old package no longer exists in SB 4.0, so any code using @EntityScan must update its imports and the new module must be on the classpath.
Spring Framework 7.x reverted to depending on commons-logging directly (architectural change from Spring 6.x's spring-jcl bridge). The enforcer rule that bans commons-logging:commons-logging had to allow it specifically when it comes from Spring Framework 7.x.
Verified with a full
mvn clean install(all modules pass — including 5 Spring autoconfigure test configurations and Quarkus integration tests).