| commit | 86c9d942452d82a479d499ffe61695a983f16bba | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Fri Jun 30 13:41:19 2017 +0200 |
| committer | Marcel Hlopko <hlopko@google.com> | Mon Jul 03 09:04:54 2017 +0200 |
| tree | 6cfba810a9cfa6e1d64df2e894c310b2f9247ad4 | |
| parent | e3312d97ab356d71cc5b6965de80b2189d547b80 [diff] |
//src:derived_java_srcs: use jar from JAVABASE instead of PATH The genrule //src:derived_java_srcs so far assumed to find the needed tool jar(1) on PATH. This, however, is not true in all setups. Instead, use jar from JAVABASE, which should be the correct toolchain to be used on the execution platform. Fixes #3284. Change-Id: I1f972f819786b511237c448a6c57484a76f4118b PiperOrigin-RevId: 160634222
{Fast, Correct} - Choose two
Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google‘s software, and thus it has been designed to handle build problems present in Google’s development environment, including:
A massive, shared code repository, in which all software is built from source. Bazel has been built for speed, using both caching and parallelism to achieve this. Bazel is critical to Google's ability to continue to scale its software development practices as the company grows.
An emphasis on automated testing and releases. Bazel has been built for correctness and reproducibility, meaning that a build performed on a continuous build machine or in a release pipeline will generate bitwise-identical outputs to those generated on a developer's machine.
Language and platform diversity. Bazel's architecture is general enough to support many different programming languages within Google, and can be used to build both client and server software targeting multiple architectures from the same underlying codebase.
Find more background about Bazel in our FAQ.