We are happy to announce that the new name for the technology formerly known as Java EE is….[insert drumroll]… Jakarta EE.
Almost 7,000 people voted in our community poll, and over 64% voted in favour of Jakarta EE. Thanks to everyone who voted, blogged, or tweeted! This has been quite the process, and we are all really happy with the community support throughout.
As we have been making progress on migrating Java EE to the Eclipse Foundation there have been a lot of moving pieces and parallel threads, especially around naming. Thankfully, we think we are getting to the end of this, and the names at least are starting to sort themselves out. We have prepared this handy table to assist with the translation from the old names to the new names.
| Old Name | New Name |
| Java EE | Jakarta EE |
| Glassfish | Eclipse Glassfish |
| Java Community Process (JCP) [*] | Jakarta EE Working Group (Jakarta EE) |
| Oracle development management | Eclipse Enterprise for Java (EE4J) Project Management Committee (PMC) |
Note that permission for products to formally use the Jakarta EE trademark will be dependent upon passing a as-yet-to-be-defined compatibility program run by EE.next. However, as of today, it is preferred that when you are generically referring to this open source software platform that you call it Jakarta EE rather than EE4J. EE4J, the Eclipse Top-level project, is the only name we’ve had for a couple of months, but as we at least tried to make clear, that was never intended to be the brand name.
Update: Fixed a typo plus the formatting of the Glassfish row in the translation table.
Update 2: [*] To be clear, the Java Community Process will continue to exist and to support the Java SE and ME communities. However, it will not be the place where Jakarta EE specifications will be developed.
Update 3: Corrected the name of the working group from EE.next to Jakarta EE.
