| tag | 253177d19f10d02ca04566a7fdfac3a5f0719471 | |
|---|---|---|
| tagger | The Android Open Source Project <initial-contribution@android.com> | Thu Feb 08 11:04:58 2024 -0800 |
| object | c069542ea944ef61896f1d629061fe650541ade1 |
Android Studio 2023.3.1-canary8 (11392117)
| commit | c069542ea944ef61896f1d629061fe650541ade1 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Feb 01 16:06:45 2024 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Feb 01 16:06:45 2024 +0000 |
| tree | f159b25e98e02fe11c05ccb1bfb40120a404ac8b | |
| parent | 909f71a545c4dc1897604022141f3d6dc9469669 [diff] | |
| parent | 8ea66c939fcdebf71db116f45d93623f6f3a8d93 [diff] |
Snap for 11390309 from 8ea66c939fcdebf71db116f45d93623f6f3a8d93 to studio-jellyfish-release Change-Id: I930d336efb8d5dff428cc21894e829fa7416bf7a
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