Fixes: build issues due to jvm tool chain

[AjeshRPai]

Fixes build issue #1539 due to tool chain. Toolchain for other modules were removed in the PR

[gemini-code-assist]

Summary of Changes

Hello @AjeshRPai, 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 resolves a critical build issue by standardizing the Kotlin JVM target configuration across several Jetcaster modules. The changes involve migrating the JVM target declaration within the Gradle build scripts to ensure consistency and compatibility, thereby fixing a regression introduced in a prior refactoring.

Highlights

• Build Configuration Standardization: I've updated the Kotlin JVM target configuration in several build.gradle.kts files. Specifically, the jvmToolchain(17) declaration within the top-level kotlin block has been replaced by kotlinOptions { jvmTarget = "17" } nested inside the android block. This change standardizes the configuration across modules.
• Build Issue Resolution: This pull request directly addresses and fixes build issue #1539, which was caused by an inconsistent JVM toolchain configuration. This inconsistency was a regression introduced by a previous PR (#1526) that removed toolchain configurations from other modules.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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 fixes a build issue caused by a conflict with the JVM toolchain configuration in several modules. The changes replace the jvmToolchain setting with kotlinOptions.jvmTarget, which is a valid and effective fix for the problem. This approach makes the build more dependent on the local developer environment's JDK version. While the current fix is acceptable to unblock the build, investigating the root cause of the toolchain conflict could be a valuable follow-up to make the build process more robust. Overall, the changes are correct and consistently applied across all affected modules.

[jaya98777]

b1ef44c