Skip to content
This repository was archived by the owner on May 14, 2026. It is now read-only.

chore: Manage errorprone and j2objc versions in pom-parent#3948

Merged
lqiu96 merged 1 commit into
mainfrom
lqiu96-patch-1
Oct 15, 2025
Merged

chore: Manage errorprone and j2objc versions in pom-parent#3948
lqiu96 merged 1 commit into
mainfrom
lqiu96-patch-1

Conversation

@lqiu96

@lqiu96 lqiu96 commented Oct 15, 2025

Copy link
Copy Markdown
Member

Versions are managed here:

<errorprone.version>2.38.0</errorprone.version>
<j2objc-annotations.version>3.0.0</j2objc-annotations.version>

third-party-deps pom already inherits from pom-parent, so there should not be any difference:

<parent>
<groupId>com.google.api</groupId>
<artifactId>gapic-generator-java-pom-parent</artifactId>
<version>2.62.4-SNAPSHOT</version><!-- {x-version-update:gapic-generator-java:current} -->
<relativePath>../../gapic-generator-java-pom-parent</relativePath>
</parent>

@lqiu96 lqiu96 requested review from blakeli0 and zhumin8 October 15, 2025 20:49
@product-auto-label product-auto-label Bot added the size: xs Pull request size is extra small. label Oct 15, 2025
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @lqiu96, 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 centralizes the management of 'errorprone' and 'j2objc-annotations' dependency versions. By removing their explicit version declarations from 'java-shared-dependencies/third-party-dependencies/pom.xml', these versions are now expected to be inherited from a parent POM, streamlining dependency version control across the project.

Highlights

  • Error Prone Version Management: The 'errorprone.version' property has been removed from 'java-shared-dependencies/third-party-dependencies/pom.xml'.
  • J2ObjC Annotations Version Management: The 'j2objc-annotations.version' property has been removed from 'java-shared-dependencies/third-party-dependencies/pom.xml'.
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.

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

Copy link
Copy Markdown
Contributor

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 refactors the management of errorprone.version and j2objc-annotations.version by moving their definitions to the parent POM. This is a good practice for centralizing dependency version management and improving maintainability. The changes in java-shared-dependencies/third-party-dependencies/pom.xml correctly remove the now-redundant properties. The change is clean and I see no issues.

@sonarqubecloud

Copy link
Copy Markdown

@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Passed Quality Gate passed for 'java_showcase_integration_tests'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@lqiu96 lqiu96 merged commit a1b5ba3 into main Oct 15, 2025
65 checks passed
@lqiu96 lqiu96 deleted the lqiu96-patch-1 branch October 15, 2025 21:06
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

size: xs Pull request size is extra small.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants