| commit | 59d2a6a8cdfcae1935a9e91ec329a6ff68fa7d5b | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Tue Jan 03 16:15:06 2017 +0000 |
| committer | John Cater <jcater@google.com> | Tue Jan 03 16:44:37 2017 +0000 |
| tree | 2201200fc8549204b8444013948d31cb48c63d16 | |
| parent | c2d0c66c7d555b13e45182bea2fb3feef2ea6052 [diff] |
Refactor JavaSkylarkApiProvider to source its info from passed-in providers instead of getting them from the base. This is a preparatory change to allow aspects to bind JavaSkylarkApiProvider with a different name. java_proto_library needs to be able to advertise its jars from each aspect. The elegant way to do this would be to bind the "java" skylark provider. Unfortunately, proto_library also advertises this provider, even though it is incorrect to do so in the context of java_proto_library, because the jars advertised by the base configured target are certainly not going to be produced. Unless we can override providers when the merged configured target is produced, we then need to be able to bind a java provider with a different name. Unfortunately the implementation of this accesses providers from the configured target, which again belong to the proto_library, not the aspect. This CL allows the java skylark api provider to serve data defined at construction time rather than from hard-coded providers from the configured target. -- PiperOrigin-RevId: 143445977 MOS_MIGRATED_REVID=143445977
{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.