The Jakarta EE 11 launch builds on earlier Core Profile (December 2024) and Net Profile (March 2025) variations and represents a big development in simplifying enterprise Java for cloud-native growth, Eclipse stated. Microsoft and Pink Hat have been among the many firms that participated within the growth of the discharge. “Our collaboration with esteemed companions IBM, Pink Hat, and Oracle has been instrumental in supporting Jakarta EE 11 runtimes on Azure, together with Azure Kubernetes Service, Azure Pink Hat OpenShift, and App Service,” Microsoft’s Scott Hunter, vp of product, Azure developer expertise, stated in an announcement.
Jakarta EE 11 has been verified to work with Java 17 and Java 21, each of that are long-term help (LTS) releases of Java SE (Customary Version). Concurrency enhancements are supported for Java 21 together with help for digital threads, which improves scalability, reduces overhead, and provides important efficiency features, stated Eclipse. Future plans name for supporting the upcoming JDK 25 LTS launch, because of arrive in September, in Jakarta EE 12, which is focused for launch in 2026.
All Jakarta EE releases are primarily based on the Jakarta EE Platform specification. Streamlined Jakarta EE 11 specs embrace a modernized Expertise Compatibility Equipment (TCK) designed to enhance compatibility testing and scale back limitations to including new checks because the platform evolves, Eclipse stated. Managed Beans has been deprecated for elimination to attain a less complicated and extra fashionable programming mannequin, whereas Context and Dependency Injection (CDI) enhancements promise extra constant utility habits. Different streamlined specs cowl Java data help, for broader integration for information integrity and diminished boilerplate code, and the elimination of Java SE Safety Supervisor, to allow extra fashionable safety practices. Software upgrades in Jakarta 11 transfer the platform from Apache Ant and Java Take a look at Harness to JUnit 5 and Apache Maven for enhanced effectivity and relevance, Eclipse stated. Updating the TCK to a multi-dependency Maven venture boosts compatibility testing and removes limitations to including new checks.
