| commit | 81e53bbc650eed42c02aeb1bbb91b44ea7d1365a | [log] [tgz] |
|---|---|---|
| author | adt-prebuilt-drop-releaser <adt-prebuilt-drop-releaser@google.com> | Thu May 16 14:27:14 2024 -0700 |
| committer | adt-prebuilt-drop-releaser <adt-prebuilt-drop-releaser@google.com> | Thu May 16 14:27:28 2024 -0700 |
| tree | e1ec713bf1d570a0c43cdee5c003739a0ccdb78f | |
| parent | e6a55e6c8b251857fa02ac4df8cca4dec27b28f6 [diff] |
Update Studio prebuilts to ab/11852314 - JBR17 - Linux - JBR17 - Windows - JBR17 - Mac Intel - JBR17 - Mac aarch64 Change-Id: I33cbdc747a589bc53eb7bb3536d62ee1c22f278d
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