Skip to content

Conversation

@kabir
Copy link
Collaborator

@kabir kabir commented Nov 17, 2025

There are boms for:

  • the core sdk classes
  • the reference classes (includes core sdk)
  • the extras classes (includes core sdk)

Fixes #461

There are boms for:
* the core sdk classes
* the reference classes (includes core sdk)
* the extras classes (includes core sdk)
@kabir
Copy link
Collaborator Author

kabir commented Nov 17, 2025

@ChenKangQiang Does this look like what you had in mind?

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @kabir, 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 significantly enhances the A2A Java SDK's usability for external developers by introducing a structured Bill of Materials (BOM) system. This system simplifies dependency management, allowing users to easily integrate SDK modules into their projects (whether vanilla Java, Spring Boot, or Quarkus-based) by importing a single BOM, which automatically handles compatible versions of all transitive dependencies.

Highlights

  • Introduction of Maven BOMs: Three new Bill of Materials (BOMs) have been added: "a2a-java-sdk-bom" for core SDK modules, "a2a-java-sdk-reference-bom" for reference implementations (including Quarkus), and "a2a-java-sdk-extras-bom" for extra modules.
  • Comprehensive Documentation: A detailed "boms/README.md" file has been added, explaining the purpose, usage, internal maintenance strategy, and automated testing of these BOMs.
  • Automated Integration Testing: Each BOM includes dedicated integration tests using "maven-invoker-plugin" and a custom "DynamicBomVerifier" to ensure all declared dependencies resolve correctly and all managed classes can be loaded, preventing version conflicts and missing dependencies.
  • Internal Project Usage Strategy: The project explicitly states that these BOMs are for external consumption only and will not be imported internally, with the parent "pom.xml" remaining the single source of truth for internal dependency management.
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 introduces Bill of Materials (BOMs) for managing dependencies, which is a great improvement for the project's consumers. The implementation is solid, including a comprehensive testing strategy using the maven-invoker-plugin to validate the BOMs. My review focuses on a few inconsistencies in the BOM definitions and their corresponding tests to ensure correctness and maintainability.

@kabir
Copy link
Collaborator Author

kabir commented Nov 18, 2025

/gemini review

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 introduces Bill of Materials (BOMs) for the SDK, extras, and reference modules, which is a fantastic addition for consumers of this library. The implementation is very well-structured, especially the integration testing strategy using maven-invoker-plugin and a dynamic class verifier. My feedback focuses on making the test utilities more robust and maintainable, and ensuring dependency scopes are correctly defined in the new BOMs.

boms/README.md Outdated
<dependency>
<groupId>io.github.a2asdk</groupId>
<artifactId>a2a-java-sdk-extras-bom</artifactId>
<version>0.4.0.Alpha1-SNAPSHOT</version>
Copy link
Collaborator

Choose a reason for hiding this comment

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

We should use the property here too :)

boms/README.md Outdated
<dependency>
<groupId>io.github.a2asdk</groupId>
<artifactId>a2a-java-sdk-reference-bom</artifactId>
<version>0.4.0.Alpha1-SNAPSHOT</version>
Copy link
Collaborator

Choose a reason for hiding this comment

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

And here :)

@kabir
Copy link
Collaborator Author

kabir commented Nov 18, 2025

@fjuma updated

@kabir kabir merged commit 22f5b1d into a2aproject:main Nov 18, 2025
10 checks passed
@jmesnil jmesnil added this to the 1.0.0 milestone Dec 11, 2025
kabir added a commit to kabir/a2a-java that referenced this pull request Dec 23, 2025
There are boms for:
* the core sdk classes
* the reference classes (includes core sdk)
* the extras classes (includes core sdk)

Fixes a2aproject#461
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.

[Feat]: Provide Bom

3 participants