| commit | 3c5e55ff8e058b624ce26e803ff00434c70d4b91 | [log] [tgz] |
|---|---|---|
| author | Liam Miller-Cushon <cushon@google.com> | Tue Jan 10 19:55:08 2017 +0000 |
| committer | Marcel Hlopko <hlopko@google.com> | Tue Jan 10 20:45:39 2017 +0000 |
| tree | d1c33057ae97300bc763f5321d838bc45da3f4d6 | |
| parent | 4d3dbbc0417e8b5994fa49c80e4273b82803cfb2 [diff] |
Invoke javac using the API, instead of main() This unifies the test and production javac invocations. Location arguments (e.g. classpath, sources) are now set programatically from Paths, instead of going through string args. The classloader masking plugin is now just a custom filemanager, since javac uses the same context for the entire compilation and we don't need a plugin to carry it across annotation processing rounds. -- PiperOrigin-RevId: 144110025 MOS_MIGRATED_REVID=144110025
{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.