Skip to content

internal: Update sbt to 1.11.5 and add JDK 24+ options#296

Merged
xerial merged 1 commit intomainfrom
chore/update-sbt-jdk25
Jan 12, 2026
Merged

internal: Update sbt to 1.11.5 and add JDK 24+ options#296
xerial merged 1 commit intomainfrom
chore/update-sbt-jdk25

Conversation

@xerial
Copy link
Copy Markdown
Member

@xerial xerial commented Jan 12, 2026

Summary

  • Update sbt from 1.10.11 to 1.11.5
  • Add JDK 24+ JVM options to suppress warnings about sun.misc.Unsafe memory access

Test plan

  • Verify sbt launches without warnings on JDK 24+
  • Verify builds work correctly

🤖 Generated with Claude Code

Add --sun-misc-unsafe-memory-access=allow and --enable-native-access
flags for JDK 24+ to suppress warnings about sun.misc.Unsafe usage.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@xerial xerial enabled auto-merge (squash) January 12, 2026 08:02
@github-actions github-actions Bot added the internal Non-user facing changes label Jan 12, 2026
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @xerial, 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 modernizing the project's build infrastructure by updating the sbt version and enhancing compatibility with the latest Java Development Kit releases. The changes are designed to provide a more stable and warning-free development experience, particularly for users operating on JDK 24 and beyond, by addressing specific JVM-related warnings.

Highlights

  • sbt Version Update: The sbt version has been upgraded from 1.10.11 to 1.11.5, ensuring the project uses the latest stable release of the build tool.
  • JDK 24+ Compatibility: New JVM options have been added specifically for JDK 24 and newer versions to suppress warnings related to sun.misc.Unsafe memory access, improving compatibility and reducing console noise.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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
Copy Markdown
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 updates the default sbt version to 1.11.5 and adds specific JVM options for JDK 24+ to handle warnings related to sun.misc.Unsafe. The changes are logical and address the stated goals. I've found one minor issue regarding an extra space in the new JVM options string which could lead to an empty argument being passed to the JVM. I've provided a suggestion to fix this for better code robustness.

Comment thread sbt
local -r v="$(java_version)"
if [[ $v -ge 17 ]]; then
if [[ $v -ge 24 ]]; then
echo "$default_jvm_opts_common --sun-misc-unsafe-memory-access=allow --enable-native-access=ALL-UNNAMED"
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.

medium

There's an extra space between the common options and the new JDK 24+ options. When the output of this function is processed by read -r -a on line 655, this double space will result in an empty string element in the extra_jvm_opts array. While many JVMs might ignore an empty argument, it's cleaner and more robust to avoid it. Please remove the extra space.

    echo "$default_jvm_opts_common --sun-misc-unsafe-memory-access=allow --enable-native-access=ALL-UNNAMED"

@xerial xerial merged commit ba64682 into main Jan 12, 2026
10 checks passed
@xerial xerial deleted the chore/update-sbt-jdk25 branch January 12, 2026 08:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Non-user facing changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant