| commit | 6817a6fcdd4275f9d3d4c3b9451a6c4144adcee1 | [log] [tgz] |
|---|---|---|
| author | Michael Staib <mstaib@google.com> | Mon Oct 05 15:58:23 2015 +0000 |
| committer | Laszlo Csomor <laszlocsomor@google.com> | Tue Oct 06 07:03:20 2015 +0000 |
| tree | 83a0a735ac0c48f777ed4a8ac06881262e2a2e50 | |
| parent | 1c0543c626bf29eda95348c5c97391bc5d372fa3 [diff] |
Allow Java libraries to export and propagate proguard_specs. It may be the case that a library used by Java clients is also used by Android clients, but when used for the latter, it requires a particular Proguard configuration. This change modifies Java library rules to accept Proguard specs and pass them up to Android rules. Note that this does not cause Proguard to be used on normal Java binaries. RELNOTES[NEW]: java_library now supports the proguard_specs attribute for passing Proguard configuration up to Android (not Java) binaries. -- MOS_MIGRATED_REVID=104661799
{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.