The Jakarta EE Team is proud to announce that Eclipse Glassfish 5.1 is now Java EE compatible and will be showing up on the official Compatibility page in short order! This is a major milestone for the overall Java EE contribution and migration to the Eclipse Foundation. The release of Eclipse Glassfish 5.1 demonstrates that all of the code required to build the Glassfish application server now resides in open-source repositories using the Eclipse Public License. The official Java EE 8 CTS (Compatibility Test Suite) was used to test and verify the resulting application server — over 44,000 tests! This is no small feat — as anybody who has ever dealt with CTS in the past will attest. Congratulations to the worldwide team that helped make this happen!
Note that this statement of compatibility is for Java EE 8 and not Jakarta EE 8. Although all of the CTS tests do now reside in the various Eclipse GitHub repositories, and we’re making great strides on running these tests against the Eclipse Glassfish deliverable, we still have work to do to declare a build as being Jakarta EE 8 compatible. Getting all of the tests to pass successfully is just one part of the puzzle.
The Jakarta EE Specification Committee is working on defining what it means to be Jakarta EE 8 compatible. From a technical viewpoint, Jakarta EE 8 will be equivalent to Java EE 8. This means there will be no additional specifications in Jakarta EE 8. There will be no modified specifications either — no API or behavioral changes will be allowed. And, of course, no new profiles will be defined. Using Java semantics, Jakarta EE 8 == Java EE 8. This is a base assumption that we’ve been living by during this process.
Jakarta EE 8
Following the basics defined by the Eclipse Foundation Specification Process (EFSP), we know the Jakarta EE 8 release needs to consist of the following:
- Specifications (documents and APIs)
- TCKs (source and binaries)
- Compatible Implementations (at least one, available under open source license)
And, in order to produce the above artifacts, some new processes need to be defined. First off, a derivative of the EFSP for the Jakarta EE Specification Process needs to be completed. Next, the Jakarta EE TCK process needs to be defined –- a goal that is nearing completion. Other items that are being investigated include artifact publishing guidelines, branding processes, and logo usage guidelines.
The Eclipse Foundation is making excellent progress. Having Eclipse Glassfish 5.1 pass the Java EE 8 compatibility tests is a huge milestone. The Jakarta EE 8 release is looking to become reality this year. And then the real fun begins when the team starts to define Jakarta EE 9!