| commit | beccb9bfee87fb4869b5c00abd9400ebaf647bf0 | [log] [tgz] |
|---|---|---|
| author | Lukacs Berki <lberki@google.com> | Tue Oct 06 11:16:31 2015 +0000 |
| committer | Laszlo Csomor <laszlocsomor@google.com> | Tue Oct 06 11:41:00 2015 +0000 |
| tree | ee8bfb4adb21ef6076044f7b6e1e11795c5bb111 | |
| parent | fb8ee791d3b39f294bf4e083b972aee2ac6f8e27 [diff] |
Implement the prefix stripping for Java resources. This CL sure works, but it leaves a few call sites for JavaSemantics#getJavaResourcePath() which make me uncomfortable. RELNOTES: Java rules now support a resource_strip_prefix attribute that allows the removal of path prefixes from Java resources. -- MOS_MIGRATED_REVID=104748537
{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.