Skip to content

Conversation

@ehsavoie
Copy link
Collaborator

@ehsavoie ehsavoie commented Oct 7, 2025

Tests are failing on Java 25 because of a classloading issue if uwing vertx json codec instead of Jackson object mapper.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @ehsavoie, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on resolving critical build and runtime issues that arise when the application is run on Java 25. The core problem, a classloading conflict related to Vert.x's JSON codec, is addressed by migrating Server-Sent Events (SSE) JSON serialization to use Jackson's ObjectMapper. This change, coupled with an upgrade to Quarkus platform version 3.28.2, significantly enhances the application's compatibility and stability with newer Java environments, allowing previously excluded tests to run successfully.

Highlights

  • Quarkus Platform Upgrade: The Quarkus platform version has been updated from 3.28.1 to 3.28.2, bringing in potential fixes and improved compatibility.
  • JSON Serialization Fix for Java 25: JSON serialization for Server-Sent Events (SSE) in A2AServerRoutes.java has been switched from Vert.x's Json.encodeToBuffer() to Jackson's ObjectMapper. This change directly addresses classloading issues encountered when running on Java 25, ensuring proper data serialization.
  • Re-enabled Integration Test: A Maven profile (java24-exclude-vertx-incompatible-tests) that previously excluded JpaDatabasePushNotificationConfigStoreIntegrationTest.java on Java 24+ has been removed. This indicates that the underlying compatibility issues preventing the test from running on newer Java versions have been resolved.
  • Code Cleanup: Unused imports have been removed from JpaDatabasePushNotificationConfigStoreIntegrationTest.java and SendStreamingMessageResponse.java, contributing to cleaner code.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/build-and-test.yml
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request addresses a build failure on Java 25 by upgrading the Quarkus platform version and switching from the Vert.x JSON codec to Jackson's ObjectMapper for Server-Sent Events (SSE) serialization. The changes are logical and seem to correctly resolve the described classloading issue. I have added one comment regarding an opportunity to reduce code duplication in A2AServerRoutes.java to improve maintainability. Overall, this is a solid fix.

@ehsavoie ehsavoie changed the title Fixing building on Java 25. fix: Fixing build on Java 25. Oct 7, 2025
Removing the use of vertx json to serialize to String.

Signed-off-by: Emmanuel Hugonnet <ehugonne@redhat.com>
@kabir kabir merged commit 59a5f68 into a2aproject:main Oct 8, 2025
8 checks passed
@ehsavoie ehsavoie deleted the jdk_25 branch December 11, 2025 08:23
kabir pushed a commit to kabir/a2a-java that referenced this pull request Dec 23, 2025
Tests are failing on Java 25 because of a classloading issue if uwing
vertx json codec instead of Jackson object mapper.

Signed-off-by: Emmanuel Hugonnet <ehugonne@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants