Cloud Native Java at the Eclipse Foundation - Not your parent's Eclipse!
summary
Eclipse becomes the hub for Cloud Native Java by taking Jakarta EE out of Oracle control (Java EE → Jakarta EE namespace migration), open‑sourcing the TCK and moving ~50+ projects and ~100+ repos (60M LOC including TCK) into a public process. MicroProfile standardizes JVM microservices with many implementations (Open Liberty, Quarkus, Helidon, WildFly). AdoptOpenJDK joins as Adoptium (AdoptOpenJDK), Eclipse offers GitLab hosting in Europe, Che/Theia cloud IDEs, and working groups to manage compatibility and certification.
AI-written summary · about
chapters (9)
- 0:00Start
- 6:29First Eclipse Working Groups
- 17:23Governance
- 18:54Working Groups
- 23:46Certification
- 33:26Micro Profile Eclipse
- 37:42Takeaways
- 44:48Will There Be some Kind of Eclipse Developer Certification in the Future
- 45:26Where Does the Name Eclipse Come from
related talks
34mJakarta EE: The Future of Cloud Native Java is Open!
40mJakarta EE and Cloud Native Projects at Eclipse Foundation
37mEclipse ❤️ Java
34mJakarta EE - Not Your Parents' Java EE
27mFrom Java EE to Jakarta EE: a user perspective
36mPractical Cloud Native Java Development with MicroProfile
46mOpening Up Java EE: Panel Discussion with Oracle, IBM, Red Hat, and the Eclipse Foundation
50mOpening Up Java EE: Panel Discussion with
