jamesfredley commented on PR #15354:
URL: https://github.com/apache/grails-core/pull/15354#issuecomment-4100696540

   ## Micronaut Spring Compatibility Note
   
   For full Micronaut integration with Spring Boot 4, we should evaluate 
upgrading to [Micronaut Spring 
6.0.0-M1](https://github.com/micronaut-projects/micronaut-spring/releases/tag/v6.0.0-M1)
 which includes:
   - Update to Spring 7 and Spring Boot 4.0.3 (PR 
micronaut-projects/micronaut-spring#810)
   - Micronaut 5 compatibility
   
   The current `grails-micronaut` module uses `micronaut-spring-boot-starter` 
via `micronautPlatformVersion=4.9.2` (Micronaut Platform 4.x), which pulls in 
Micronaut Spring 5.x targeting Spring Boot 3.x. Micronaut Spring 6.0.0-M1 
targets Micronaut 5.x milestones, so adopting it would require updating the 
Micronaut stack as well.
   
   **Recommendation:** Evaluate Micronaut Spring 6.0.0-M1 once Micronaut 5 
reaches a stable release, or pin 
`io.micronaut.spring:micronaut-spring-boot-starter:6.0.0-M1` directly if 
Micronaut integration is tested and needed before then.
   
   ## 8.0.x Merge Status
   
   Merged latest `8.0.x` into this branch. Post-merge fixes applied:
   - Removed vendored Spring theme files reintroduced by merge (already removed 
in #15457)
   - Removed `LoaderImplementation` usage reintroduced by merge (removed in 
Spring Boot 4)
   - Removed theme references from `GrailsApplicationContext` reintroduced by 
merge
   - Added missing `SessionFactoryUtils` vendored import in 
`GrailsOpenSessionInViewInterceptor`
   - Added `spring-boot-hibernate` dependency for test example package 
relocation
   
   **Remaining:** `GrailsWebApplicationContext` and 
`grails-data-mongodb-spring-boot` still reference removed Spring theme APIs and 
need the same treatment. Additionally, `ApplicationClassInjectorSpec` needs 
updating for the new autoconfigure package path.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to