The Eclipse Foundation has officially launched Jakarta EE 11, marking a significant advancement in enterprise Java development with full support for both Java SE 17 and Java SE 21. In this exclusive VMblog Q&A, Tanja Obradovic, Senior Manager of Java Programs at the Eclipse Foundation, breaks down the key features that make this release a game-changer for developers, including the introduction of Jakarta Data specification, virtual threads support, and completely modernized Test Compatibility Kits (TCKs) that replace legacy Apache Ant tooling with JUnit 5 and Apache Maven.
Building on the momentum of the Core Profile launch in December 2024 and the Web Profile release in March 2025, Jakarta EE 11 represents the culmination of community-driven efforts to make enterprise Java simpler, more consistent, and better suited for cloud-native development. With over 420 open source projects under the Eclipse Foundation umbrella and a clear roadmap toward Jakarta EE 12 in 2026, this release positions the platform for continued growth and innovation in the enterprise Java ecosystem.
++
VMblog: Before we jump into the news, give us a bit of background on the Eclipse Foundation.
Tanja Obradovic: The Eclipse Foundation is a Brussels-based open source software foundation and one of the largest open source foundations in the world. While we’re perhaps best known for the Eclipse IDE, used by millions of developers, and for Jakarta EE, the open source successor to Java EE, or Eclipse Temurin, one of the most widely used OpenJDK Java distributions, our scope extends far beyond that. We currently host over 420 open source projects across diverse technology domains, including runtimes, tools, specifications, and frameworks for cloud and edge applications, AI, automotive, IoT, systems engineering, open processor designs, regulatory compliance, and many others. We also serve as the home for industry collaborations such as Adoptium, Software Defined Vehicle, and OpenHW.
VMblog: What exactly are you announcing today?
Obradovic: Today, we’re formally launching Jakarta EE 11, the latest version of the Jakarta EE Platform, an open, community-driven specification framework for enterprise Java. This release builds on the momentum of the Core Profile, which launched in December 2024, and the Web Profile, which followed in March 2025. Together, these milestones represent a significant advancement in making enterprise Java simpler, more consistent, and better suited for cloud-native development.
Jakarta EE 11 introduces a range of improvements that enhance developer productivity, increase platform performance, and align the platform with the latest Java LTS releases. One of the most important aspects of this release is that it fully supports both Java SE 17 and Java SE 21, allowing developers to confidently adopt modern Java features while relying on a stable and mature enterprise framework.
VMblog: What is included in this version that should catch the eye of developers?
Obradovic: Jakarta EE 11 offers a number of enhancements that make it easier and faster for developers to build enterprise applications. The inclusion of support for Java SE 21 is particularly important, as it enables developers to utilize multiple new features, including the highly popular virtual threads. The use of Java records continues in this release as well, making applications more expressive and scalable, and helping teams write cleaner, more maintainable code.
Another key feature in this release is the introduction of Jakarta Data, a brand new specification that brings a standard repository pattern to Jakarta EE. Developers familiar with Spring Data will find this model intuitive and efficient. It simplifies data access and eliminates much of the boilerplate code that typically accompanies database interactions.
On top of that, Jakarta EE 11 also modernizes the testing infrastructure behind the platform. The updated Test Compatibility Kits, or TCKs, represent a major investment in the future of Jakarta EE. This work makes it easier for contributors to create new tests and for vendors to validate their implementations using modern tools and workflows.
VMblog: Why are the modernized TCKs such a big deal?
Obradovic: The updated TCKs are a major step forward for the Jakarta EE ecosystem. They help ensure that compatible implementations of the platform meet the required specifications, and they do so in a way that is much more accessible to the broader developer community.
Previously, the TCKs were based on legacy tooling such as Apache Ant and the Java Test Harness. In Jakarta EE 11, these have been replaced with tools that most developers already use today, including JUnit 5 and Apache Maven. This shift alone makes writing and running tests much more familiar and efficient.
The structure of the TCKs has also been improved. The project layout is now simpler and more modular, which reduces complexity and makes it easier to maintain. Contributors can get started faster, and the barrier to entry for new vendors or developers looking to participate has been significantly lowered.
Perhaps most importantly, these improvements position Jakarta EE to handle future growth more easily. As new specifications are added to the platform, creating compatibility tests will be a smoother process. That makes it more practical to innovate and evolve the platform over time without adding unnecessary complexity.
VMblog: That sounds like a lot of improvements! What should the ecosystem expect next?
Obradovic: Now that Jakarta EE 11 is available, the community is already working toward Jakarta EE 12. The next release is planned for 2026 and will raise the platform’s API source level to Java SE 21. It is also expected to support Java SE 25 at runtime, ensuring continued alignment with Java’s long-term support strategy.
Jakarta EE 12 is shaping up to be another significant release. The community is exploring updates across nearly all specifications, and we may see new additions such as Jakarta Query and enhancements to Jakarta NoSQL and Jakarta MVC. There is also active discussion around modern alternatives to Enterprise Beans, with a strong focus on leveraging CDI as the central programming model.
Looking ahead, Jakarta EE will continue to aim for a two-year release cadence. This rhythm provides stability and predictability for both developers and vendors while allowing enough time to deliver meaningful improvements. Anyone interested in contributing or staying informed is encouraged to connect with the community through jakarta.ee/connect/.
##
Tanja Obradovic is the Senior Manager, Java Programs at the Eclipse Foundation. Ms. Obradovic has over two decades of leadership experience in the Java ecosystem, including pivotal roles at Oracle, BEA Systems, and other enterprise software organizations. Tanja played a key role in the formation of Jakarta EE and now leads a team dedicated to growing and evolving the Eclipse Foundation’s Java-related and tooling working groups.
