Skip to content

8.0.0-M6

Pre-release
Pre-release
Compare
Choose a tag to compare
@arjantijms arjantijms released this 16 May 17:19
· 715 commits to master since this release

Eclipse GlassFish 8 is an application server, implementing Jakarta EE. This release is corresponding with the Jakarta EE 11 M3 specification under development.

glassfish-8

Jakarta EE 11 M3 is the third milestone release of Jakarta EE 11. GlassFish 8 M6 incorporates a subset of this. The final versions of the Security APIs and Jakarta Faces have been added and implemented, while the final Servlet 6.1.0 API has been added but not everything implemented yet. The REST 4.0.0 API has been added as well.

New in M6 are the proposed final APIs of the Wave 6 specs authentication, concurrency, faces and the wave 7 spec security.

8.0.0-M6 also incorporates all changes from the 7.0.x branch.

The following is the full list of Jakarta EE 11 proposed final and M3 APIs included:

API Implementation
jakarta.el-api.version 6.0.0 Expressly 6.0.0-M1
jakarta.annotation-api.version 3.0.0
jakarta.cdi-api.version 4.1.0 Weld 6.0.0.Beta1
jakarta.interceptor-api.version 2.2.0 Weld 6.0.0.Beta1
jakarta.rest-api.version 4.0.0 Jersey 4.0.0-M1
jakarta.servlet-api.version 6.1.0 (internal in GlassFish 8.0.0-M6)
jakarta.pages-api.version 4.0.0 WaSP 4.0.0-M1
jakarta.websocket-api.version 2.2.0 Tyrus 2.2.0-M1
jakarta.authorization-api.version 3.0.0 Exousia 3.0.0-M3
jakarta.authentication-api.version 3.1.0 Epicyro 3.1.0
jakarta.persistence-api.version 3.2.0 EclipseLink 5.0.0-B02
jakarta.validation-api.version 3.1.0 Hibernate Validator 8.0.1.Final
jakarta.security-api.version 4.0.0 Soteria 4.0.0
jakarta.concurrent-api.version 3.1.0 Concurro 3.1.0-M3
jakarta.faces-api.version 4.1.0 Mojarra 4.1.0

JDK 17 is available for the special JDK 17 build, but this build is only intended for TCK purposes.
For the regular version of GlassFish 8, JDK 21 is required as a minimum and the final version of GlassFish 8 is targeted to certify on JDK 21 for Jakarta EE 11.

In this release GlassFish itself compiles, builds and passes the internal tests executed during a build. The Security, Authorization, Authentication and Faces TCK passed completely. The PR verification tests all pass as well.

Being an early access milestone build, this build should obviously only be used for testing. Not all of the updated APIs are truly final and are subject to change. Some of the proposed final APIs are currently in staging and are undergoing a ballot for their final release.

What's Changed

Full Changelog: 8.0.0-M5...8.0.0-M6