While we are still looking into initiating ballots for the Jakarta EE Platform and the Profiles any day now, I wanted to let you know about the hold up!
The issues we are facing are related to passing the TCK for the Compatible Implementation. Here is the current status on the release!
Jakarta EE 10 Status
- CDI Language Model TCK
- GlassFish hit a problem with the new tests added in the service release
- Need CDI team to respond
- Tracking issue is https://github.com/jakartaee/cdi-tck/issues/392
- Platform
- TCKs passed with GlassFish so far
- Concurrency TCK: with the new PR, GlassFish will get 9 test failures
- Web Profile
- Failures with remote EJB, ear package
- Issue: https://github.com/jakartaee/concurrency/issues/244
- Change is not complete. The PR will cause platform regression but the change is not complete yet.
- To be discussed on July 6th during the Platform TCK call
- Issue: https://github.com/jakartaee/concurrency/issues/244
- Failures with remote EJB, ear package
- Core Profile
- XML Binding use in Rest TCK https://github.com/jakartaee/rest/issues/1109 (TCK challenge that applies to Web Profile)
- XML Binding (TCK) is optional for Full Platform + Web Profile implementations as per https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/user_guides/jakartaee/src/main/jbake/content/intro.adoc (search for `Jakarta XML Binding`).
If you are interested in finding out more, please consider attending the Jakarta EE Platform Project calls (every Tuesday @11 am EST) published on the Jakarta EE Specification Calendar, or follow the meeting minutes!
In any case, we are only a couple of weeks away! Ultimately all Release Review PRs are ready.
- Jakarta EE Platform Specification 10 - https://github.com/jakartaee/specifications/pull/498
- Jakarta EE Web Profile 10 - https://github.com/jakartaee/specifications/pull/497
- Jakarta EE Core Profile 10 - https://github.com/jakartaee/specifications/pull/495
