| tag | a462bd5e49e391cd63fe1e698a7ab687f22e91ec | |
|---|---|---|
| tagger | The Android Open Source Project <initial-contribution@android.com> | Thu May 09 11:36:50 2024 -0700 |
| object | 8b85898b8d8ceca273dd00e09649d91573c56d30 |
Android Studio 2024.1.1-canary8 (11792637)
| commit | 8b85898b8d8ceca273dd00e09649d91573c56d30 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Apr 18 07:25:38 2024 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Apr 18 07:25:38 2024 +0000 |
| tree | 0c5ab750bb8df2387f787c6fa10fd231615add79 | |
| parent | b31d780fed2ae594ea2809f6f05cf851e376b1f2 [diff] | |
| parent | e6a55e6c8b251857fa02ac4df8cca4dec27b28f6 [diff] |
Snap for 11731333 from e6a55e6c8b251857fa02ac4df8cca4dec27b28f6 to studio-koala-release Change-Id: I21c49fe8e16b4c84f8f93aeefa0ce328e37e0ae6
By default Bazel uses --bootclasspath bazed on current java runtime. Such default don't works well when Studio java versions being updated: e.g. for JBR21 update for 2023.3 and 2024.1 releazes we want to target java 17, but have an option to run Studio and test using java 21.
But java code is not always able to compile against newer sdk. We extract bootclasspath for each java runtime version, and use it together with -source -target options.
Bazel 7 changes attributes for bootclasspath rule. To migrate to new version replace host_javabase and target_javabase with single java_runtime_alias
See also:
bazel build --verbose_failures --subcommands=pretty_print --toolchain_resolution_debug=java /... bazel query //prebuilts/studio/jdk/jdk17:java17_compile_toolchain --output=build