Why Oracle Handed Java EE Over to Eclipse Foundation – What It Means for Developers

Oracle announced that it has chosen the Eclipse Foundation as the new home for Java EE, a decision made together with the platform’s other major contributors, IBM and Red Hat.

Oracle evangelist David Delabassee wrote in a blog that the Eclipse Foundation’s extensive experience with Java EE and related technologies will help accelerate the transition, create community‑friendly processes, and leverage complementary projects such as MicroProfile.

Eclipse Foundation executive director Mike Milinkovich expressed optimism, saying the move is exactly what Java EE needs and what the community has been hoping for.

Milinkovich emphasized that open source is the best path for successful innovation and collaboration, especially as many enterprises shift toward cloud‑centric models. Handing Java EE to the Eclipse Foundation offers vendors a better opportunity for cooperation, enabling individuals, small companies, enterprises, and large vendors to work together on a reliable platform that supports faster innovation.

He noted that Java EE will undergo the same project‑approval process as other Eclipse projects and is likely to become a top‑level project, encompassing roughly 40 Java Specification Requests (JSRs).

Delabassee said Oracle plans to re‑license its Java EE technologies, including the GlassFish reference implementation, technology compatibility kits (TCKs), and related documentation, to the Eclipse Foundation. A new brand name for the platform is being considered but has not yet been decided.

The exact timeline for the transition is still uncertain, but Oracle hopes to begin shortly after Java EE 8 is completed to facilitate a rapid shift. During the transition, Oracle will continue to support existing Java EE license holders, including those migrating to Java EE 8, and will maintain support for current and future WebLogic Server versions that incorporate Java EE 8.

Delabassee concluded that the plan allows Oracle to continue supporting the existing Java EE standard while moving it onto a more open development path. Although much work remains, the effort is on the right track.

Commentary in the article reflects that Java EE, a collection of technologies such as EJB, Session Beans, messaging, and buses, has matured over the past decade. While it may not die, it is gradually aging, and Oracle’s decision suggests the standard no longer offers significant commercial value. The move does not fundamentally change Java itself, but it highlights the slower pace of Java’s evolution compared with other languages.

Overall, the handover is seen as a hopeful step toward a more open and innovative future for Java EE.