website

☕ Pulse on Java – April 2026 Edition

Your AI-generated monthly roundup of Java platform, framework, and community updates. [infoq.com], [openliberty.io], [keycloak.org], [spring.io], [docs.gradle.org], [blog.jetbrains.com], [quarkus.io]

April 2026 was a dynamic month in the Java world, marking a post-JDK 26 landscape where the community shifted focus toward long-term support releases, new previews, and aligning frameworks with the latest Java capabilities. Java SE 26 entered mainstream use with its first set of patch updates, and work on JDK 27 gained pace: key enhancements (including refined pattern matching) were confirmed for the upcoming release, and the JDK 27 release schedule was finalized. Meanwhile, enterprise Java continued building on the newly delivered Jakarta EE 11 platform, with updates like Open Liberty’s April release adding Java 26 support and addressing security, and debate swirling around which new features (e.g. Jakarta NoSQL) will shape Jakarta EE 12. Popular Java frameworks and libraries rolled out a mix of maintenance patches and significant previews of what’s coming next, from a flurry of Spring 4.1 release candidates with new features to updates in Quarkus, Micronaut, and Helidon improving integration with modern Java features. Build tools also advanced, with Gradle 9.5 bringing enhanced diagnostics and improved plugin development support, and Maven 3.9.15 shipping another maintenance release as the community awaits Maven 4.0 GA. On the security front, the quarterly Oracle Critical Patch Update (CPU) in mid-April delivered important JDK updates (and the initial JDK 26.0.1), addressing vulnerabilities across all supported Java versions. Below we present the key April 2026 events and releases by date and category, followed by detailed highlights across Java SE, enterprise Java, frameworks, tools, community happenings, and security. [infoq.com], [infoq.com] [docs.gradle.org], [docs.gradle.org] [versionlog.com] [infoq.com]

Visualization

[infoq.com], [keycloak.org], [spring.io], [infoq.com], [infoq.com], [blog.jetbrains.com], [quarkus.io]

🔬 Java SE & Platform Updates

JDK 27 Release Schedule Finalized: In mid-April, Mark Reinhold (Chief Architect, Java Platform Group at Oracle) announced the proposed release schedule for JDK 27 after a brief review period. Under this plan, JDK 27 will reach Rampdown Phase One on June 4, Rampdown Phase Two on July 16, initial Release Candidate on August 6, and General Availability on September 14, 2026. This keeps Java’s regular six-month cadence on track. The OpenJDK community is already locking in features: JEP 532 (Primitive Types in Patterns, instanceof, and switch – Fifth Preview) was moved to Proposed to Target for JDK 27 in early April, reaffirming Java’s commitment to fully supporting pattern matching for primitive types across all contexts. Meanwhile, JEP 535 (Shenandoah GC: Generational Mode by Default) was promoted to Candidate status in April for a likely JDK 28 inclusion – paving the way to make Generational Shenandoah the new default mode and deprecate the current non-generational implementation. [infoq.com] [infoq.com]

Post-JDK 26 Updates and Java 8/11 Support: Following Java 26’s March GA release, the community swiftly shifted to ensure its stability. On April 21, the Oracle Critical Patch Update (CPU) rolled out OpenJDK 26.0.1 – the very first patch for JDK 26 – in parallel with corresponding updates for Java 25, 21, 17, 11, and 8. These releases, also incorporated by major OpenJDK distributors (BellSoft, Azul, Amazon Corretto, etc.), address dozens of security vulnerabilities and bugs across all maintained versions. Notably, the initial JDK 26.0.1 includes routine fixes like updated cryptography libraries and hotspot stability improvements. While Java 8 and Java 11 no longer receive free public updates (having reached their end-of-free-support milestone in January), those still on these legacy LTS versions can obtain April’s critical fixes through paid support or third-party JDK builds. With Java 17 (now in its fifth year) and Java 21 (recent LTS) solidifying their role as the de facto long-term support baselines, the emphasis is on adopting modern Java versions for optimal security and performance. [infoq.com], [jdk.java.net] [infoq.com] [jdk.java.net]

Inside Java Happenings & JDK Project News: The OpenJDK community buzzed with activity. The official Inside Java Newscast episodes this month dove into JVM technical topics: Episode #109 (early April) featured Nicolai Parlog exploring advanced JVM diagnostics and new tools for analyzing crash dumps in production. By the end of April, Inside Java Newscast #111 with Billy Korando highlighted improvements to Java’s constructors (e.g., flexible instantiation logic via JEP 513 “Flexible Main Methods” in JDK 25) and tips for safer object initialization. These bite-sized updates continue to provide developers with insights into Java’s evolving internals and upcoming features. Meanwhile, the community at large celebrated the arrival of JDK 26: public webinars, blog posts, and podcasts (on Foojay, Inside Java, and others) examined the top new capabilities in Java 26, from AOT object caching (Project Leyden) to HTTP/3 support and garbage collection optimizations. With Java 26 firmly in hand, attention is turning to JDK 27 and beyond, where bigger changes like Valhalla’s value objects and post-quantum cryptography loom on the horizon. [techlife.blog], [techlife.blog]

🏢 Jakarta EE & Enterprise Java

Jakarta EE 12 Progress and Debate: The Eclipse Jakarta EE community made incremental strides toward Jakarta EE 12, which is expected in late 2026. In early April, Jakarta Persistence 4.0 (JPA) delivered a second milestone with new types like ComparableExpression and NumericExpression for stronger type safety in criteria queries. Several other EE 12 specification updates (e.g. Jakarta Connectors 3.0, JSF 5.0, Transactions 2.1) approached their Milestone 2 drafts, although some open questions – such as whether to include Jakarta NoSQL in EE 12 – remain under discussion in the community. The overriding theme for EE 12, tentatively dubbed “Robust and Flexible”, reflects the focus on resilience and adaptability. For now, Jakarta EE 11 continues to be the current stable platform, and vendors are aligning their products with its APIs and Java 21/25 support while the next release is carefully shaped. [infoq.com] [infoq.com]

Enterprise Java Runtime Updates: A number of Jakarta EE platform implementations shipped updates in April to refine features and patch issues:

Open Liberty 26.0.0.4 (April 21) – IBM’s open-source Java/Jakarta EE server rolled out a new GA release, adding official JDK 26 compatibility and implementing improvements from its earlier beta. Notable features include enhanced JWT authentication (administrators can specify acceptable signing algorithms via JOSE headers for added security) and removal of the default LTPA keys password to address a prior vulnerability (CVE-2025-14917). These measures strengthen Liberty’s security stance while fully embracing Java 26 and providing dynamic tooling registration via the new mcpServer-1.0 feature. [infoq.com] [infoq.com]
Payara Platform Community 7.2026.4 – The April update of the Payara Server (Jakarta EE 11) prioritized code cleanup, bug fixes, and dependency updates. Among improvements were the removal of several deprecated internal APIs and properties, plus performance tuning (e.g. optimizing cache invalidation for Jakarta Data queries). While largely a maintenance release, Payara’s consistent monthly cadence ensures its Jakarta EE 11 runtime stays robust and secure for users. (Note: The Payara Enterprise edition also received a 6.37.0 patch in April, backporting key fixes to the Jakarta EE 10 stream for commercial customers.) [docs.payara.fish], [docs.payara.fish]
Eclipse GlassFish – The Jakarta EE 11 reference implementation continued its development, including the integration of Grizzly 5.0 (GlassFish’s NIO framework) which takes advantage of virtual threads (Project Loom) for scalability. While GlassFish itself did not issue a new GA in April, these improvements in its infrastructure will benefit downstream projects (like Payara) and test the waters for Java’s latest features in enterprise scenarios. [manorrock.com]
Keycloak 26.6.0 (April 8) – The popular open-source identity and access management server, based on Quarkus and often used with Java enterprise applications, saw a major feature release. Keycloak 26.6.0 introduces powerful new capabilities: full support for JWT-based OAuth2 client authentication (RFC 7523), “federated” client identity bridging to reuse credentials from external identity providers, scriptable administrative workflows (for user & client lifecycle tasks) now stable, a redesigned Keycloak Testing Framework on JUnit 6 for improved testability, and zero-downtime patching within a cluster (rolling upgrades) to minimize maintenance disruptions. This ambitious release brings Keycloak to the forefront of modern IAM requirements, aligning it with the latest Jakarta and MicroProfile standards, and highlighting the growing importance of identity management in Java cloud deployments. [infoq.com] [keycloak.org]

Other Enterprise News: The Eclipse MicroProfile project, which complements Jakarta EE with microservice APIs, did not release a new version in April. However, MicroProfile 6.1 is already widely adopted (with Jakarta EE 10 compatibility), and work is ongoing toward MicroProfile 7 planned for late 2026 to align with EE 12. In the security arena, beyond Oracle’s CPU, one noteworthy vulnerability was CVE-2026-22750, disclosed on April 9 in Spring Cloud Gateway 4.2.0. The flaw caused custom spring.ssl.bundle configurations to be silently ignored – a potentially serious oversight since it might leave systems using default TLS settings unintentionally. The 4.2.x line of Spring Cloud Gateway is no longer publicly maintained, so non-commercial users are urged to upgrade to SCG 5.0.2 or 5.1.1 (the latest supported open-source releases) where a fix is available. This case underscores the importance of staying current with supported versions of critical infrastructure libraries. [spring.io], [spring.io] [spring.io]

🚀 Major Framework Releases & Ecosystem News

Spring Ecosystem: Patches and New Release Candidates

Building on its major Spring Framework 7 / Spring Boot 4 rollout from last year, the Spring team continued to iterate rapidly in April. On April 23, they delivered Spring Boot 4.0.6 – a patch release bringing dozens of bug fixes, dependency upgrades, and minor enhancements to the latest GA line. Not stopping there, the week of April 20 was marked by a flurry of Spring previews: the first release candidates (RC1) of Spring Boot 4.1.0 and several related projects (Spring Security 7.1, Spring Integration 7.1, Spring Modulith 2.1, Spring AMQP 4.1, Spring for Apache Kafka 4.1, Spring LDAP 4.1, Spring Vault 4.1, etc.) became available. These RCs showcase upcoming features, such as built-in support for OpenTelemetry’s OTLP protocol in Boot 4.1, new authorization manager capabilities in Spring Security 7.1, enhancements to Spring Integration’s Redis and JMS modules, improvements for modular monolith architectures in Spring Modulith 2.1, and updated components across the portfolio. These early releases signal that the Spring ecosystem intends to quickly leverage Java’s latest features (like JDK 26 support and Virtual Threads) and refine its frameworks for cloud-native and AI-infused use cases (Spring AI 1.2 continues in development). With GA versions of Spring Boot 4.1.x expected in the coming weeks, Spring developers can anticipate a seamless pivot to the next iteration of the framework by mid-2026, with even better observability and integration features. [infoq.com], [infoq.com] [infoq.com]

Other notable Spring-related updates include the resolution of CVE-2026-22750 affecting Spring Cloud Gateway 4.2.0 (as discussed above in Security), and ongoing Spring Cloud roadmap alignment: the next Spring Cloud “2026.x” release train will target Boot 4.x/Framework 7, though it had not yet been finalized by April. [spring.io]

Other Frameworks & Libraries: Quarkus, Micronaut, Helidon & More

Outside Spring, numerous Java frameworks saw steady progress:

Quarkus 3.34.x – Red Hat’s Quarkus, a leading Java/Kubernetes runtime, followed up its recent LTS switch (with Quarkus 3.33 designated as the new Long-Term Support release in late March) by issuing Quarkus 3.34 as a short-lived feature stream. On April 23, Quarkus 3.34.6 was released as the final patch for 3.34, wrapping up improvements and preparing users to transition to the LTS branch. Quarkus 3.34 provided various enhancements over 3.33, including internal optimizations and dependency updates, while still requiring Java 17+ (Java 21 recommended) to tap its full potential. Looking ahead, Quarkus 3.35 was already on the horizon by month’s end (arriving in early May) with experimental features like JAR classpath tree-shaking and profile-guided optimizations (PGO) for native images – foreshadowing the performance and footprint improvements that Quarkus 4 aims to deliver later in 2026. [quarkus.io], [quarkus.io]
Micronaut 4.10.x – The Micronaut framework maintained its rapid release tempo, issuing three incremental updates in April: v4.10.11 (April 1), v4.10.12 (April 17), and v4.10.13 (April 28). These versions primarily addressed bug fixes, dependency upgrades, and minor improvements across Micronaut’s modules (Web, Data, etc.), ensuring solid support for JDK 21 and 25 and smoothing the path for enterprise usage. Meanwhile, plans for Micronaut 5.0 continued to take shape, with the team considering raising the baseline to JDK 25 and leveraging new Java features like Scoped Values (JDK 21) to further speed up the framework. The Micronaut community largely supports the move to embrace the latest JDK, signaling that 2026 may see the framework join others in requiring modern Java versions for new major releases. [techlife.blog], [techlife.blog]
Apache Helidon 4.4.1 – Oracle’s microservices framework Helidon (which comes in SE and MP flavors) published v4.4.1 in April, a maintenance update that nonetheless delivered interesting features. Helidon 4.4.1 added support for the Smile binary JSON format in its Web Server, introduced configuration to supply a custom LangChain4j McpClient (allowing integration with large language model services via the Model Context Protocol), and restored certain environment variable handling behaviors to maintain backward compatibility. These changes demonstrate Helidon’s efforts to keep pace with evolving trends like AI assistants (via LangChain4j connectivity) and to continuously refine developer experience in cloud-native Java applications. [infoq.com] [infoq.com], [infoq.com]
Hibernate ORM 7.3.0.Final – The predominant JPA implementation Hibernate delivered a new minor release (7.3) in early April with a mix of bug fixes and developer enhancements. Among the highlights, Hibernate 7.3 introduces a KeyType enumeration that simplifies usage of entity manager find() methods for natural keys, and a new @NaturalIdClass annotation to define composite natural identifiers, making it easier to load entities by natural keys in one call. These features enrich JPA providers’ capabilities for handling alternate identifiers beyond primary keys, benefiting enterprise applications that rely on meaningful business keys. [infoq.com]
LangChain4j 1.13.0 – The Java library for integrating large language models (LangChain4j) saw a formal 1.13.0 release in April, alongside its 23rd beta iteration. The new version’s notable additions include persistent & recoverable AI agent “memory” (via new classes to save and restore an agent’s internal state), improved loading of custom agent “skills” from the classpath, and a new HibernateContentRetriever for fetching data using HQL queries. These enhancements are part of the broader push to make AI integration on the JVM more developer-friendly – allowing Java applications to embed and manage AI agents without leaving the Java ecosystem. LangChain4j’s advancement, together with Spring’s AI modules and JetBrains’ Koog agent framework (which got a Java integration in late March), highlights the Java community’s momentum in embracing AI-driven application development in 2026. [infoq.com]

Build Tools & JVM Languages

April saw continued progress in build tooling and other parts of the Java ecosystem:

Gradle 9.5.0 – The Gradle Build Tool’s fast-moving 9.x line added another incremental release. Gradle 9.5 arrived on April 28 and brought a range of productivity improvements for build engineers. Diagnostics & reporting got a boost: task provenance information is now included in error messages and build reports (pointing to the plugin or script that registered a failing task, making it easier to trace errors). Plugin development was simplified with type-safe Kotlin accessors for precompiled settings plugins, enabling better IDE auto-completion and compile-time checking for custom plugin logic. Additional enhancements include new options to control the client–daemon network address for Gradle in restrictive environments, improved help output and Tooling API capabilities, and more. Gradle 9.5.0 continues to require JDK 17+ to run (like 9.0+), and supports building on Java 26 out of the box. The Gradle team’s public roadmap suggests further performance optimizations and potential auto-enablement of the configuration cache in upcoming releases. [docs.gradle.org] [docs.gradle.org], [docs.gradle.org] [versionlog.com], [versionlog.com]
Maven 3.9.15 – The Apache Maven project released version 3.9.15 on April 13 as a maintenance update to the 3.x line. This likely represents one of the final 3.9.x updates as Maven 4.0 nears GA. Maven 3.9.15 primarily includes documentation updates and dependency upgrades. In the meantime, Maven’s long-awaited major version 4.0 (RC5 was released November 2025) remained in release-candidate stage through April, with the Maven team focusing on addressing any remaining bugs and ensuring broad plugin compatibility before a full GA. Maven 4 will require Java 17 and bring significant enhancements (faster dependency resolution, improved POM model, better error messages, etc.). It is expected to finally ship later in 2026, ushering Maven’s first major version change in over a decade and challenging teams to update any outdated build scripts. [versionlog.com]
Other Tools & Languages: JetBrains delivered a bugfix update to IntelliJ IDEA (2026.1.1) on April 23, rectifying issues with Gradle integration and application server management. On the language front, Kotlin’s team continued development of the upcoming Kotlin 2.x features (for example, releasing Kotlin 2.3.20 with standard library enhancements in late March), while Google’s Agent Development Kit (ADK) for Java hit version 1.1.0 in April, broadening its support for building AI chat applications on the JVM (including new ChatCompletions API support and integration of DeepMind’s Gemma LLM in its model registry). [blog.jetbrains.com] [blog.jetbrains.com] [infoq.com], [infoq.com]

🌐 Java Community & Events

April saw a mix of virtual and in-person Java community events across the globe. The JavaLand 2026 conference took place in Germany (early April) and showcased sessions on JDK 26’s features, cloud architectures, and Spring Boot 4 adoption. Meanwhile, the Java® on Microsoft team held JDConf 2026 (late March) focusing on “agentic” AI solutions in Java, and the Open Community eXperience (OCX) 2026 event (formerly known as EclipseCon) was held on April 13–15, highlighting open-source collaboration but facing attendance challenges due to overlapping with other European Java conferences. [blogs.eclipse.org]

Finally, the Java ecosystem media continued to produce rich content for developers. The Java Annotated Monthly (JetBrains) for April curated analyses of the Java 26 release, insights into fast startup techniques (Project Leyden’s ahead-of-time caching), and how frameworks like Spring and Quarkus are adapting to Java’s new features. Community blogs on sites like Foojay, InfoQ, and TechLife discussed topics such as making Java more cloud-native (CRaC checkpoints, Java containers on Kubernetes), the growing synergy between Java and AI/ML (with tooling like Spring AI and Koog), and practical guidance for migrating from legacy Java versions to Java 21/25 LTS. All in all, April 2026 underscored how the Java landscape—spanning language evolution, enterprise standards, open-source frameworks, and developer tools—continues to innovate and coalesce around the latest Java platform, with an eye on performance, cloud readiness, and emerging technologies like AI. [blog.jetbrains.com], [techlife.blog]