A2A Java SDK 1.0 Reaches General Availability
The Agent2Agent (A2A) Java SDK has reached its 1.0 general availability release, graduating from the beta that shipped in May. The SDK provides a typed Java client for Google's Agent-to-Agent protocol, enabling standardized communication between AI agents built on different frameworks and platforms.
The GA release introduces an integration test kit featuring a Quarkus-based agent designed for cross-SDK interoperability testing, ensuring that Java-based agents can reliably communicate with agents built using other language SDKs. The A2AHttpResponse interface and A2AClientHTTPError class now expose HTTP response headers, giving developers finer-grained control over error handling and response inspection.
For Java teams building agentic applications, the 1.0 milestone signals production readiness. The A2A protocol complements the Model Context Protocol (MCP) by focusing specifically on agent-to-agent coordination rather than agent-to-tool connectivity, and having a stable Java SDK lowers the barrier for enterprise adoption where Java remains the dominant backend language.
Read more — InfoQ
Jakarta EE 12 Core Profile Specifications Approach Milestone Releases
Jakarta EE 12 development is progressing steadily, with all specifications in the Core Profile either having produced or about to produce milestone releases. Jakarta EE Developer Advocate Ivar Grimstad confirmed that a majority of specifications in the Web Profile and full Platform are also in a healthy state.
Several specifications are currently working through their Milestone 2 releases, including Jakarta Connectors 3.0, Jakarta Faces 5.0, Jakarta Transactions 2.1, and Jakarta JSON Processing 2.2. Meanwhile, GlassFish 8.0.3 has filed compatibility certification requests for both the EE 11 Platform and Core Profile 11, positioning it as a potential early certifier for the Core Profile 12 ratification process.
The steady progress across all three profile tiers suggests Jakarta EE 12 remains on track for its planned release window, giving enterprise Java developers a clear upgrade path that continues the platform's modernization trajectory started with the Jakarta namespace migration.
Read more — InfoQ
Gradle 9.6 Release Candidate Improves Configuration Cache
The second release candidate of Gradle 9.6.0 delivers improvements focused on build reliability and automation-friendliness. The headline change is improved Configuration Cache hit rates achieved through more accurate tracking of project properties set via system properties and environment variables, reducing unnecessary cache invalidations in CI/CD pipelines.
A new --non-interactive command-line option provides a cleaner signal for automated environments, explicitly suppressing prompts and interactive features without relying on terminal detection heuristics. The release also deprecates Groovy DSL implicit property and method lookup in parent projects, with removal planned for Gradle 10.0 as part of the ongoing effort to make build scripts more predictable and less reliant on Groovy-specific magic.
Read more — Gradle
Links & Sources
You May Also Enjoy
