Opening Up Java EE: Panel Discussion with
summary
Oracle transfers Java EE stewardship to the Eclipse Foundation under the EE4J 1.0 charter, with the immediate milestone of moving code (including Jersey and JAX‑RS repos) and open‑sourcing previously closed bits so the initial release can pass the Java EE 8 TCK. Timeline has no firm dates; focus is compatibility with Java 8 first, then faster, modular evolution (CDI splitting and MicroProfile specs feeding into EE4J). Vendors (IBM, Red Hat, Payara, Tomitribe) commit to contribute, and community funding or hired engineers is discussed to broaden participation.
AI-written summary · about
chapters (12)
- 0:00Java EE panel introduction
- 2:51Java EE dev process at Eclipse
- 7:17Oracle's EE4J support
- 11:42EE4J 1.0 timeline
- 19:20Why Eclipse Foundation
- 22:20EE4J integration goals
- 24:46Aligning with OpenJDK cycle
- 31:19Diversity in EE4J contributions
- 41:20Funding EE4J community
- 43:44Java package names impact
- 45:14Modularizing CDI
- 46:18Call to action
related talks
27mFrom Java EE to Jakarta EE: a user perspective
34mJakarta EE: The Future of Cloud Native Java is Open!
53mJava EE 8 and the Open Future of Java EE - What You Need to Know!
34mJakarta EE - Not Your Parents' Java EE
42mWhat's Going on With Jakarta EE
15mJakarta EE: Why and how to get involved in Open Source Software?
32mJakarta EE Community
40mJakarta EE and Cloud Native Projects at Eclipse Foundation