How to Easily Upgrade to Jakarta EE 10 Javax to Jakarta Prefix without a Hassle
summary
Step-by-step plan: run Eclipse Transformer first to convert javax→jakarta across source, resources and binary jars (it post-processes WAR/JARs and handles XML namespaces and property names, covering ~99% of cases), then run OpenRewrite to apply refactoring recipes for Jakarta EE 10 dropped APIs and JVM-level code modernizations. For stubborn third‑party libraries bundle them into a helper module, use Maven Shade to create one artifact, transform that artifact, and prefer upgrading to vendor Jakarta builds or classifier variants (example: PrimeFaces Jakarta classifier, Quartz RC).
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:32Migration challenges
- 5:53Impact of migration
- 7:13Automated tools
- 14:15Demo project overview
- 16:28Transforming artifacts
- 23:07Transforming source code
- 28:27Refactoring with OpenRewrite
- 31:44Handling tricky dependencies
- 39:10Shading for compatibility
- 45:40Q&A and conclusion
related talks
40mMigrating from Java EE to JakartaEE 10: Challenges and Opportunities
44mPaving the road with Jakarta EE and Apache TomEE
42mWhat's Going on With Jakarta EE
51mModern and Lightweight Cloud Application Development with Java and Jakarta EE
43mJakarta EE 9 and Beyond
45mEverything YOU need to Know About Jakarta EE 10
32mFrom Legacy to Legendary: Jakarta EE’s Evolution in the Modern Era
48mJakarta EE 10 Feature by Feature