However, new processes will have to be defined. In accordance with the basics defined by the Eclipse Foundation Specification Process (EFSP), Jakarta EE 8 release should include the specifications, TCKs and compatible implementations. Therefore, there will be no additional specifications in Jakarta EE 8 and no modified specifications also, no new profiles will be defined. You should also keep in mind that from a technical point of view, Jakarta EE 8 will be the same as Java EE 8, Kevin mentioned.

The good news is that t he Jakarta EE Specification Committee is already working on defining what it means to be Jakarta EE 8 compatible. Plus, as IBM’s Kevin Sutter pointed out, “t he official Java EE 8 CTS (Compatibility Test Suite) was used to test and verify the resulting application server - over 44,000 tests!”Īlthough Eclipse Glassfish 5.1 is now Java EE 8 compatible, there’s still work to be done to declare a build as being Jakarta EE 8 compatible. SEE ALSO: Checking in on Jakarta EE Meet Eclipse Glassfish 5.1įeature-wise, Eclipse Glassfish 5.1 is no different than Oracle GlassFish 5.0.1 so what’s so special about it? The latest release is Java EE compatible, which proves that “ GlassFish and all other components transferred from Oracle to Eclipse are buildable, functional and usable,” Dmitry argued in his blog post. You can download Eclipse GlassFish 5.1 here. Eclipse GlassFish 5.1 has passed all CTS/TCK tests (run on Oracle infrastructure) and has been certified as Java EE 8 compatible.” This release marks a major milestone in the transition from Java EE to Jakarta EE as Dmitry Kornilov mentioned in a recent blog post, “ all components formerly supplied by Oracle have been transferred to the Eclipse Foundation from Oracle Java EE repositories, have passed the Eclipse release review, and have been released to Maven Central with new licensing terms. Eclipse Glassfish 5.1 has been completely built by the Eclipse Foundation from the transferred and relicensed components.

Glassfish server 5.0