Jakarta EE 10 is the first major release of Jakarta EE since the “jakarta” namespace update. Many of the component Specifications are introducing Major or Minor version updates to signify key changes in their respective Specifications and APIs. The Platform and/or Web Profile Specifications will be incorporating many of these updated Specifications.
The goal of the Jakarta EE 10 release is to deliver a set of coordinated specifications across the spectrum of Jakarta EE technologies.
The Platform team sees Jakarta EE 10 as the collection of component Specifications. Some of these component Specifications are introducing breaking changes to their API, which will require an increase in the Major version of the respective Specification. Many other component Specifications are introducing updates which are binary compatible and, thus, will only require a Minor version update. Regardless of the scope of changes, all artifacts for the component and Platform Specifications will be affected – Specifications, APIs, TCKs, and Compatible Implementations.
Complementing the Web Profile, a new profile called the Core Profile is being proposed for Jakarta EE 10. The goal of the Core Profile is to define a subset of the Jakarta EE technologies which target microservices development and runtimes. It is still not clear if the Core Profile will be released in sync with the Web and Platform specifications. A separate release plan will be developed, circulated, and balloted for the Core Profile.
Java SE 11 will become the minimum runtime supported by Jakarta EE compatible implementations.
If a component Specification is planning a Major or Minor version update for Jakarta EE 10, then the recommendation would be to recompile and distribute the specification’s APIs at the Java SE 11 source and target levels. This is not a requirement since there may be reasons to continue compiling and distributing the APIs at an earlier Java source or target level.
Note: The Platform API uber jar files will all be compiled at the Java SE 11 source/target levels. This is consistent with past practices. These uber jar files will be deprecated for Jakarta EE 10 to allow for possible removal in a future release.
The TCKs will be compiled at the Java SE 11 level. In order to allow for runtimes beyond Java SE 11, the TCK will also need to be (successfully) executed with Java SE 17.
In Jakarta EE 9.1, the framework for performing API Signature tests was updated to make it easier to test Signatures across multiple Java levels. The framework and/or API tests may need to be tweaked as we continue to learn and experiment with future levels of Java.
How a Compatible Implementation supports the Java SE 11 runtime (or above) will be left as a vendor-defined solution.
Suggestions on support for JPMS modules were introduced in the Jakarta EE 9 Platform Specification. It is desired to firm up these suggestions into requirements. Several discussions via Issues, Mailing Lists, and the Platform call have resulted in these requirements for Jakarta EE 10.
module-info.class following a specified set of conventions:
jakarta.<specName> (reference names.adoc)module-info.class (guidelines will be provided)module-info.class for EE 10
The number of compatible implementations available for specification ratification is limited due to the requirement that all optional features need to be implemented and verified via the TCK. This is a current restriction due to the EFSP and our Platform specification. The EFSP is being worked on via this issue and should be resolved in the next iteration of the EFSP.
For the Platform specification, the following two features will be tagged as “removed” or “deprecated” (exact term and/or mechanism still needs to be determined).
The idea behind this tagging is to indicate that these features will no longer be required for specification ratification. These features will still be documented as “optional” in the EJB specification. And, the TCKs will still be available for verifying implementations that choose to implement these features. The Platform specification will be updated to properly reflect that these features will not be required for ratifying compatible implementations.
Each Specification project should own the TCK source and produce the TCK artifacts. This needs to be done in such a way that the artifacts can be run to validate implementations at the individual specification level, as well as integrated into platform level TCKs.
This is a run-at goal for Jakarta EE 10. We know that not all Specifications can establish their standalone TCKs in this timeframe. The Platform TCK can initiate this refactoring by breaking apart the TCK source into separate directories within the Platform TCK repository. This will help with the eventual move of these TCK directories into their respective component repositories.
As mentioned, many of the Component Specification projects have already declared their intent for either a Major or Minor version update for Jakarta EE 10. These projects have already submitted or completed their Plan Reviews for inclusion in Jakarta EE 10, and are driving towards a 4Q2021 release. These updates are outlined in the sections below.
The following details the specifications and APIs currently planned for the Jakarta EE 10 Platform and Web Profile.
List of specifications in Jakarta EE 10 Platform and Web Profile (updated specifications marked with asterisks).
The Platform and Web Profile API uber jar files will be re-generated to correspond with the Jakarta EE 10 release designation.
These API uber jar files will be compiled and distributed at the Java 11 source/target levels.
Note: These uber jars will not be modularized, per the earlier discussion.
The Jakarta EE 10 Platform release plan covers the Platform and Web Profile specifications. As stated earlier, all component Specifications which plan a Major or Minor release will be creating their own separate release plans.
We are proposing to deliver Jakarta EE 9 in a set of waves similar to those delivered in the Jakarta EE 8 release. These waves are somewhat related to the dependency tree of specifications. We aim to deliver specifications with a low number of dependencies first followed by other specifications.
The following specifications can be delivered independently of other apis.
The specifications included in Wave 1 are:
The specifications included in Wave 2 are:
The specifications included in Wave 3 are:
The specifications included in Wave 4 are:
The specifications included in Wave 5 are:
The specifications included in Wave 6 are:
The specifications included in Wave 7 are:
With the rather large Jakarta EE 10 release scope, at least one Release Candidate for Jakarta EE Platform and Web Profile will be produced. These Release Candidates will include:
Once the release candidates have been validated and any issues ironed out, the full 10 release will proceed with all deliverables required for submission to the specification committee for approval.
Since this Jakarta EE 10 release is rather large, a progress review will most likely occur as the content becomes more firm. The overall schedule for Jakarta EE 10 will be maintained on this separate page.
The JESP requires us to have a Compatible Implementation of the Full Platform and Web Profile available before the Platform Project can deliver a final Specification. Discussions are occurring with the Specification Committee to allow for additional ratified compatible implementations (besides always relying on Eclipse Glassfish). The Platform project has no control over the release dates of any potential Compatible Implementations. The platform project will maintain close coordination with the various Compatible Implementations for the duration of the Jakarta EE 10 release cycle.
Additional clarifications for this Release Plan can be found in the Jakarta EE 10 Release Plan FAQ.