Posts Tagged ‘ee4j’
And the Name Is…
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.
EE4J Code Arrives
Last week the EE4J project achieved an important milestone when the source code for the API and reference implementation of JSON-P JSR-374 project was pushed by Dmitry Kornilov into its GitHub repository in the EE4J organization. This is the first project of the initial nine proposed to reach this stage.
This may seem like a small step in a very large process, but it is a concrete demonstration of the commitment to move forward with the migration of Java EE to the Eclipse Foundation. The Oracle team and the Eclipse Foundation staff had a ton of work to do to make this possible. This is definitely one of those cases where the visible code contributions are just the visible tip of an iceberg’s worth of effort.
Here are just a few examples of the work that went on to get to this stage:
- The names of the projects such as Glassfish represent important trademarks in the industry. Oracle transferred ownership of these project names to the Eclipse Foundation so that they can be held and protected for the community.
- The EMO staff reviewed the projects proposals, ran the project creation review, provisioned the repositories and set up the committer lists.
- The Oracle team packaged up the source code and updated the file headers to reflect the new EPL-2.0 licensing.
- The EMO IP staff scanned the code and ensured that all was well before approving it for initial check-in.
Now that the collective team has run through this process with JSON-P we will be working to get the remaining eight initial projects pushed out as quickly as possible. Hopefully by the end of this month. Meanwhile, more projects will be proposed and we will be migrating a steady stream of Java EE projects into EE4J.
Exciting times!
Life at Eclipse 