| commit | 936196a5397ad056a79cfccfc6d436ccb4a3c770 | [log] [tgz] |
|---|---|---|
| author | cushon <cushon@google.com> | Wed Sep 29 11:47:25 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Sep 29 11:48:47 2021 -0700 |
| tree | 59a0a2fc147d059d30b483a7db014b8e682366c2 | |
| parent | 08f3e93d4d3a59c1fbfd08efc76c6181fdb3c9a9 [diff] |
Use a JDK version-specific toolchain in `bazel_java_test.sh` e.g. for ` //src/test/shell/bazel:bazel_java_test_jdk16_toolchain_head`, this test was previously using `@bazel_tools//tools/jdk:toolchain`, which was leaking the toolchain from the enclosing version of Bazel. It worked anyways because turbine was always producing JDK 8 class files, but as of https://github.com/google/turbine/commit/006a74b6cd7565221a2d7fe9593c103bdd83584c turbine uses the class file version corresponding to the `-target` or `--release` flag. This fixes e.g. ``` java/com/google/sandwich/B.java:3: error: cannot access C C myObject; ^ bad class file: bazel-out/k8-fastbuild/bin/java/com/google/sandwich/libbottom-hjar.jar(/com/google/sandwich/C.class) class file has wrong version 59.0, should be 55.0 Please remove or make sure it appears in the correct subdirectory of the classpath. ``` from https://github.com/bazelbuild/bazel/pull/14059 PiperOrigin-RevId: 399738050
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
