build: migrate deprecated kotlinOptions to compilerOptions

[afaqkhan707]

This change replaces the deprecated kotlinOptions.jvmTarget with the
new kotlin { compilerOptions { jvmTarget = ... } } API.

• Removes build-time deprecation warnings
• Aligns the project with current Kotlin Gradle DSL recommendations
• No functional behavior changes

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Summary of Changes

Hello @afaqkhan707, 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 refactors the build configuration to align with the latest Kotlin Gradle DSL recommendations. It replaces a deprecated method for specifying the JVM target with the modern compilerOptions block, effectively eliminating build-time warnings without altering the project's functionality or compilation targets.

Highlights

• Build Configuration Update: Migrates the project's Kotlin Gradle DSL configuration from the deprecated kotlinOptions block to the recommended kotlin { compilerOptions { ... } } structure.
• Deprecation Warning Removal: This change specifically addresses and removes build-time deprecation warnings related to kotlinOptions.jvmTarget.
• No Functional Impact: The update is purely a build configuration refactor and introduces no functional changes to the application's behavior or runtime.

🧠 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. ↩

[gemini-code-assist]

Code Review

This pull request correctly migrates app/build.gradle.kts from the deprecated kotlinOptions.jvmTarget to the new compilerOptions API. This is a good improvement to keep the project's build scripts modern. I've left one suggestion to use the type-safe enum constant for setting the JVM target. Additionally, I noticed that the advanceddeeplinkapp/build.gradle.kts file still uses the old kotlinOptions. To ensure consistency across the project and eliminate all deprecation warnings, I recommend applying the same update to that module as well.

[gemini-code-assist]

For better type safety and to avoid potential typos with string-based targets, it's recommended to use the JvmTarget enum constant directly. In this case, JvmTarget.JVM_11 should be used instead of JvmTarget.fromTarget("11").

        jvmTarget = JvmTarget.JVM_11

[dturner]

@afaqkhan707 Thanks for your contribution. In order to accept this, we need you to sign the CLA. If we don't hear back within 1 week, this PR will be closed.

[afaqkhan707]

Done