diff options
| author | David Ostrovsky <david@ostrovsky.org> | 2021-12-24 07:43:48 +0100 |
|---|---|---|
| committer | David Ostrovsky <d.ostrovsky@gmx.de> | 2022-01-20 06:40:51 -0400 |
| commit | be732c16ab1834162ed1c215a695c8b1486add9a (patch) | |
| tree | f4ee6e0fc8caae0198c8b89af638830e477aa0ad /org.eclipse.jgit/findBugs | |
| parent | c812947962103c427a202f6df38d23e1088007f1 (diff) | |
| download | jgit-be732c16ab1834162ed1c215a695c8b1486add9a.tar.gz jgit-be732c16ab1834162ed1c215a695c8b1486add9a.zip | |
Bazel: Switch to using toolchain resolution for java rules
Bump Bazel version to release 5.0.0. In this new Bazel release,
--incompatible_use_toolchain_resolution_for_java_rules is flipped, that
means that the build must be adapted to toolchain resolution.
Specification toolchain resolution for java rules is here: [1]. Main
tracking Bazel issue is here: [2].
Given that new Bazel release also added support for remote JDK 17, add
experimental support for building with remote JDK 17 to produce major
byte code version 61.
Test Plan:
To build with remote JDK 11 run:
$ bazel build :all
To build with remote JDK 17 run:
$ bazel build --config java17 :all
[1] https://docs.google.com/document/d/1MVbBxbKVKRJJY7DnkptHpvz7ROhyAYy4a-TZ-n7Q0r4/edit?usp=sharing
[2] https://github.com/bazelbuild/bazel/issues/7849
Change-Id: I8d26dff722c6677ea7642913b61e416b23ea9041
Diffstat (limited to 'org.eclipse.jgit/findBugs')
0 files changed, 0 insertions, 0 deletions