You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@causeway.apache.org by Andi Huber <ah...@apache.org> on 2026/01/25 06:57:38 UTC

Hibernate to replace EclipseLink in Version 4.x?

Spring Boot 4.1.0 will be released by end of May 2026 and the Spring 
Team released its first milestone (4.1.0-M1) last week.

Our latest releases are

  * Apache Causeway |3.5.0| on top of Spring Boot 3.5.x (End of OSS
    Support June 2026)
  * Apache Causeway |4.0.0-M1| on top of Spring Boot 4.0.x


What would make sense to me is to plan our |4.0.0-RC1| release around 
June 2026 on top of Spring 4.1.0.
And perhaps do a |4.0.0-M2| in between, for example around March 2026.
Food for thought regarding our 4.0.x:

  * Should we replace our JPA ORM provider *EclipseLink* -> *Hibernate *?
  * For all the framework provided JPA flavored extensions (/SecMan/,
    ...), should we build and release those with static weaving/bytecode
    enhancement turned on? (What are the downsides to doing so?)