| tag | df4ecfad199f4f3652f8cb4dc3519d7d97fa508a | |
|---|---|---|
| tagger | The Android Open Source Project <initial-contribution@android.com> | Wed May 15 11:43:49 2024 -0700 |
| object | e6a55e6c8b251857fa02ac4df8cca4dec27b28f6 |
Android Studio 2024.1.2-canary1 (11822507)
| commit | e6a55e6c8b251857fa02ac4df8cca4dec27b28f6 | [log] [tgz] |
|---|---|---|
| author | Jacob Logsdon <jlogs@google.com> | Thu Apr 11 21:01:17 2024 +0000 |
| committer | Jacob Logsdon <jlogs@google.com> | Thu Apr 11 21:03:47 2024 +0000 |
| tree | 0c5ab750bb8df2387f787c6fa10fd231615add79 | |
| parent | 03fa2fcdfe9b61c84aaaa838ca4ce7e80eacae93 [diff] |
Revert "Update Studio prebuilts to ab/11679475" This reverts commit 03fa2fcdfe9b61c84aaaa838ca4ce7e80eacae93. Reason for revert: b/333908428 Fixes: 333908428 Change-Id: Ia731f790821f54eb1836a9d4cc77e9c9b2be5fb0
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