| tag | e9c15e7d04d96b64ef019849b339ee7b7725d954 | |
|---|---|---|
| tagger | The Android Open Source Project <initial-contribution@android.com> | Tue Apr 30 10:19:19 2024 -0700 |
| object | 6884172b4b949a834d13d8c9ca1471814159317d |
Android Studio 2023.3.1 (11709847)
| commit | 6884172b4b949a834d13d8c9ca1471814159317d | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Mar 21 17:22:53 2024 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Mar 21 17:22:53 2024 +0000 |
| tree | 671ffa48e8677219630760fdb4da79de15f26622 | |
| parent | 71b276a3494be94d6c06daaea6fdd97780bb1785 [diff] | |
| parent | 69ce575f3f09f5f3c00d97a9a592dbbf74bb5e32 [diff] |
Snap for 11608709 from 69ce575f3f09f5f3c00d97a9a592dbbf74bb5e32 to studio-jellyfish-release Change-Id: I8d7895864b1b5569cc175ae26429369574e2546f
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