ENG-3834: Clean up pom.xml

[oschwald]

Summary

• Remove redundant <source> and <target> from maven-compiler-plugin

The <release>17</release> element is sufficient since Maven 3.6+. It sets source, target, AND cross-compilation API compatibility in one setting.

Test plan

• mvn clean test passes

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @oschwald, I'm Gemini Code Assist¹! 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 cleaning up the project's pom.xml by eliminating redundant configuration for the Maven compiler plugin. It leverages a more modern and concise approach by relying solely on the <release> element, which effectively manages source and target compatibility settings, resulting in a leaner and more maintainable build descriptor.

Highlights

• Maven Compiler Plugin Configuration: Removed redundant <source> and <target> elements from the maven-compiler-plugin configuration in pom.xml. The <release>17</release> element is now sufficient as it implicitly sets source, target, and cross-compilation API compatibility in Maven 3.6+.

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]

Code Review

This pull request cleans up the pom.xml by removing redundant <source> and <target> configurations from the maven-compiler-plugin. This is a good improvement as the <release> tag is sufficient and considered best practice for setting the Java version, simplifying the build configuration. The change is correct and improves maintainability.