Why Oracle’s Trademark Standoff Threatened Java EE’s Future

On May 4, Eclipse Foundation President Mike Milinkovic posted on his personal blog the final outcome of the trademark negotiations between Oracle and the Eclipse Foundation.

After 18 months of intensive talks, the effort collapsed completely; Oracle will not sign a trademark relinquishment agreement.

Background

In the summer of 2017, Oracle’s Java EE evangelist David Delabasse announced that Oracle would open‑source Java EE to make it more flexible and responsive to industry and technology changes.

According to the Eclipse Foundation board meeting minutes, Oracle reversed its position and presented a series of unacceptable demands that would expose the foundation to greater risk.

Oracle required that Eclipse‑distributed products such as the Eclipse IDE be bundled with Oracle’s runtime environment, prohibiting users with Oracle licenses from using any other vendor’s certification. This would strip the IDE and GlassFish of their vendor‑neutral status.

Oracle introduced this restriction after negotiations had begun, and the move is widely seen as a reaction to IBM’s OpenJ9 JVM contribution, which threatens Oracle’s Java business.

If Eclipse products lost their vendor neutrality, the foundation’s tax‑exempt status would be jeopardized, potentially leading to financial disaster and even closure of the foundation. Consequently, the foundation could not accept Oracle’s demands, and the negotiations failed.

The fallout means the end of Java EE as it was known. The Eclipse Foundation may have to rely on outdated code that cannot be modified without renaming projects and packages (e.g., JAX‑RS, javax.*). Without deep refactoring, applications would need to be recompiled for a completely new, incompatible platform, breaking the “Write Once Run Anywhere” principle and leaving no vendor willing to invest in recompilation.

Looking ahead, Oracle has exercised its veto power on the Eclipse board. The foundation had hoped Jakarta EE would inherit the Java EE standard and provide a solid framework for learning and adoption, but now developers face the prospect of overhauling existing applications for a platform that feels like a dead‑end.

Milinkovic’s blog notes that some compromises were made, yet Jakarta EE cannot offer backward compatibility and has become a “zombie” project, likened to a shattered glass bottle that has fallen to the ground.

This marks the day Oracle effectively killed Java EE.