From Spring Boot 2 to Spring Boot 3 with Java 21 and Jakarta EE
summary
Migrating a Spring Boot 2 app to Spring Boot 3 requires changing javax → jakarta across code and dependent jars, updating Spring and Jakarta versions, and fixing imports; expect compilation and test failures from transitive libs. Practical fixes shown: use the IDE refactor or OpenRewrite for source, run Eclipse Transformer (or Apache Tomcat migration tool) to rewrite bytecode jars, re-release/install updated artifacts to Maven, then tests pass. Also demonstrates using Jakarta EE 10 features (UUID primary keys) and Java 22 preview string templates and notes Jakarta EE 11 (Jakarta Data, RPC) arriving June/July.
AI-written summary · about
chapters (13)
- 0:00Jakarta EE and Spring Boot intro
- 5:02Jakarta EE relevance
- 9:40Spring Boot 2 to 3 migration
- 13:12Fixing compilation errors
- 16:00Failing tests and dependencies
- 24:58Transitive dependencies issues
- 26:50Eclipse Transformer
- 33:37Additional migration steps
- 35:05Java 22 upgrade
- 40:49Jakarta EE 10 features
- 42:14Jakarta EE 11 new
- 46:10Summary and impact
- 49:26Q&A
related talks
59mFrom Spring Boot 2 to Spring Boot 3 with Java 21 and Jakarta EE
01h 04mMind the Gap: Jumping from Spring Boot 2.x to 3.x
40mMigrating from Java EE to JakartaEE 10: Challenges and Opportunities
02h 38mJakarta in 2023, What Is the Situation?
49mHow to Easily Upgrade to Jakarta EE 10 Javax to Jakarta Prefix without a Hassle
43mMigrating to Spring Boot 3
01h 02mMigrating from Java EE: to Spring Boot or Something Else
44mPaving the road with Jakarta EE and Apache TomEE