GraalVM Native Build Tools 1.0.0 GA
GraalVM Native Build Tools has reached its first stable release at version 1.0.0 GA, marking a significant maturity milestone for developers building native Java executables with GraalVM. The 1.0.0 release stabilises the Maven and Gradle plugin APIs that teams have been using to compile Spring Boot, Micronaut, and Quarkus applications into native images with near-instant startup times.
The release includes a targeted fix for JavaApplicationFunctionalTest class failures that appeared when running Gradle tests against recent GraalVM JDK distributions. Those failures were triggered by internal GraalVM APIs that had been removed, and the 1.0.0 release adapts the test harness accordingly. The release also ships dependency upgrades to align with the latest GraalVM SDK.
For teams targeting cloud-native deployments on Kubernetes or AWS Lambda, the 1.0.0 label means that plugin upgrade paths are now governed by semantic versioning, giving CI pipelines a stable contract. The official Maven coordinates are org.graalvm.buildtools:native-maven-plugin:1.0.0 and org.graalvm.buildtools.native for Gradle.
Read more — GraalVM Native Build Tools
EclipseLink 5.0.0 GA — Jakarta EE 11 Persistence
EclipseLink 5.0.0 has reached general availability, delivering full support for the Jakarta Persistence 3.2 specification as part of the Jakarta EE 11 umbrella. This is the reference implementation for JPA 3.2 and makes EclipseLink the first JPA provider to ship a GA release against the new specification, ahead of the Hibernate ORM 7.x timeline.
Jakarta Persistence 3.2 in EclipseLink 5.0 brings enhanced JPQL capabilities, including improved type-safe query construction and expanded criteria API support. Database platform improvements in this release span Oracle, MySQL, DB2, and PostgreSQL, with query optimizations specific to each engine's newer feature sets. Security and logging subsystems received refinements to reduce noise in production environments and improve auditability.
Developers migrating from EclipseLink 4.x to 5.0 should expect to upgrade their Jakarta EE dependencies to EE 11 versions (jakarta.persistence:jakarta.persistence-api:3.2.0). Applications running on GlassFish 9 or Payara with Jakarta EE 11 profiles can adopt EclipseLink 5.0 without additional compatibility shims.
Read more — Eclipse Foundation
Open Liberty 26.0.0.3 GA
Open Liberty 26.0.0.3 is now generally available, following the beta that shipped earlier in March with MCP Server support. The GA release focuses on two key additions: a new getUsersByAttribute() method in the UserRegistry interface, and support for the latest Jandex index format.
The getUsersByAttribute() method enables programmatic lookup of users by custom LDAP or identity store attributes, which is valuable in enterprise deployments where user resolution depends on non-standard fields like employee IDs or department codes. This was a frequently requested API gap that required workarounds in previous releases.
Jandex index format upgrades are a runtime-level optimisation. Jandex produces the annotation index that Liberty and CDI frameworks use to discover beans, providers, and extensions at startup. By supporting the latest Jandex index format, Open Liberty 26.0.0.3 delivers faster startup times for large applications with many annotated classes — a meaningful improvement for containerised workloads where cold start latency matters.
Read more — Open Liberty
Quarkus 3.34.0
Quarkus 3.34.0 ships as the latest in the project's continuous delivery cadence. The headline change is the deprecation of the ObjectLoader interface, which has been an internal implementation detail tightly coupled to Gizmo 1's bytecode generation strategy. Applications that reference ObjectLoader directly should migrate away, as the interface will be removed in a future release when Gizmo undergoes its next major revision.
On the API surface, the PathTree interface gains a new getResourceNames() method, giving extension authors and framework integrators a cleaner way to enumerate resources within a path tree without relying on lower-level file system scanning. This is a quality-of-life improvement for developers building Quarkus extensions that process classpath resources at build time.
The 3.34.0 release continues Quarkus's bi-weekly cadence and includes the standard set of dependency upgrades aligned with the quarterly Quarkiverse maintenance cycle.
Read more — Quarkus
Infinispan 16.2.0.Dev01 — Redis Protocol Expansion
Infinispan 16.2.0.Dev01 is the first development milestone in the 16.2.x series, signalling active work on the features that will appear in the next minor release. Two areas stand out for developer impact: expanded Redis Serialization Protocol (RESP3) command support, and a switch to OpenAPI v3 for the REST API specification.
RESP3 support in this build gains four new commands: BITFIELD for atomic integer operations on string values, SUBSCRIBE and PUNSUBSCRIBE for pub/sub messaging patterns, and DIGEST for data integrity verification. Teams using Infinispan as a Redis-compatible caching layer in their Spring Boot or Quarkus applications can now use a broader subset of standard Redis client libraries without adapter shims.
The REST API specification has been migrated from OpenAPI v2 (Swagger) to OpenAPI v3. This means generated clients, API gateway configurations, and developer portal integrations built against Infinispan's REST API should be regenerated from the new OpenAPI v3 schema. The change aligns Infinispan with the tooling ecosystem that has largely standardised on OAS3, including Spring Doc and the Quarkus OpenAPI extension.
Read more — Infinispan
Links & Sources
You May Also Enjoy
