| tag | c934dba1d3a6f90f9ed5c038ee90b90cd190f244 | |
|---|---|---|
| tagger | Dmitry Lomov <dslomov@google.com> | Tue Jul 12 13:56:10 2016 +0200 |
| object | 37e0ff1423e8f562b8bdf80b8dbab417a23756b6 |
0.1.5 Release 0.1.5 (2016-02-05)
Baseline: 3a95f35
Extra cherry picks:
+ 068a661: GPLv2 + Classpath exception compliance: ship the source code of jformatstring
+ a18add1: Adds the source of the checker framework
+ f6c24de: GPLv2 + Classpath exception compliance: ship the source of checker_framework
+ c95cb5f: Add source for Javac
+ 4017d28: Fix fallout of incorrectly merged review (3921)
+ 8378cd8: Rollback of commit
a9b84575a32476a5faf991da22b44661d75c19b6.
Incompatible changes:
- Set stamping to false by default (i.e., --nostamp)
- Removed --objc_dump_syms_binary.
- Removes --objc_gcov_binary flag.
- Remove JAVAC "Make" variable
- The startup flag --blaze_cpu is removed,
New features:
- A new java test runner that support XML output and test filtering
is supported. It can be used by specifying --nolegacy_bazel_java_test
or by specifying the test_class attribute on a java_test.
- Skylark aspects can now specify configuration fragment
dependencies with fragments and host_fragments like rules can.
Important changes:
- Support for downloading remote resources through proxies by
setting HTTP_PROXY (or HTTPS_PROXY).
- Timestamps within Android apks are removed to make apks
deterministic.
- Support aggregation over existing rules in Skylark extensions
through native.rules and native.rule.
- A tools/bazel script in the workspace will be executed
as an opportunity to use a fixed version of Bazel (not
implemented for the homebrew recipe yet).
- --noimplicit_deps and --nohost_deps work correctly for Aspect
attributes.
- JDK-related targets are now available via @local_jdk (instead of
@local-jdk).
- j2objc tools can now be accessed via @bazel_j2objc, not
@bazel-j2objc.
- Repository rules must use names that are valid workspace names.
- [rust] Update to Rust 1.6
- Add support for .tar.xz archives to http_archive rules.
- Make C++ modules compatible with tools using
--compilation_prerequisites_only
- [d] Update to DMD 2.070.0
| commit | 37e0ff1423e8f562b8bdf80b8dbab417a23756b6 | [log] [tgz] |
|---|---|---|
| author | Dmitry Lomov <dslomov@google.com> | Tue Jul 12 13:56:10 2016 +0200 |
| committer | Dmitry Lomov <dslomov@google.com> | Tue Jul 12 13:56:10 2016 +0200 |
| tree | c9667674a7b00649e620bba4a72075a855e187df | |
| parent | 1c339d246b5078bc5e0f9cfd9d945110b2763f7e [diff] |
Updated CHANGELOG with source cherry-picks
{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.