What's Going on With Jakarta EE
summary
Jakarta EE 9 focuses on three concrete goals: lower entry barriers by removing rarely used and deprecated APIs, javax → jakarta rename to perform the namespace switch, and easy migration by minimizing API changes so existing Java EE 8 apps mostly need package fixes. Specs require at least one open‑source compatible implementation and open TCKs. Planned work includes split CTS into per-spec suites, updating properties from java x to jakarta, adding missing @Deprecated/@Repeatable annotations, and weekly platform calls plus a target final release before summer. Contributions start by signing the Eclipse ECA and sending GitHub pull requests.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker intro
- 1:49Jakarta EE overview and website
- 3:02Jakarta Specification Process
- 6:12Jakarta EE specifications and TCK
- 9:40Focus areas of Jakarta EE 9
- 13:40Namespace migration to Jakarta
- 17:55Contributing to Jakarta EE
- 23:42Ways to contribute beyond coding
- 31:37Resources and community engagement
- 38:10Q&A and closing
related talks
43mJakarta EE 9 and Beyond
39mJakarta EE 9 and Beyond
40mJakarta EE and Cloud Native Projects at Eclipse Foundation
15mJakarta EE: Why and how to get involved in Open Source Software?
34mJakarta EE: The Future of Cloud Native Java is Open!
02h 38mJakarta in 2023, What Is the Situation?
48mJakarta EE 10 Feature by Feature
32mPrepare for Jakarta EE 11!