| tag | b5a034c1e1d12ddcd6b1cbff4b6283d5662124e5 | |
|---|---|---|
| tagger | Dmitry Lomov <dslomov@google.com> | Tue Jul 12 16:49:16 2016 +0200 |
| object | 850fe1b13ec470bac7a5b48ad338b2f2700ce2f5 |
0.2.0 0.2.0 Release 0.2.0 (2016-02-18)
Baseline: 9e100ac
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)
Incompatible changes:
- ObjC compile actions for J2ObjC-translated code now only has
access to headers from the java deps of the associated original
java rule.
These compile actions no longer takes the compiler options
specified in "copts" attribute on objc_binary/ios_test rules.
J2ObjC dead code removal (enabled through flag
"--j2objc_dead_code_removal") now happens *after* ObjC
compilation.
- maven_jar no longer supports separate artifact_id, group_id, and
verison fields. This information should be provided in the
artifact field,
instead.
New features:
- Better support for toolchains that don't have a dynamic linker.
- build_file_content attribute added to new_git_repository,
new_http_archive, and new_local_repository.
- Add support for .tar.bz2 archives to http_archive rules.
Important changes:
- The --skyframe flag is no longer available for the build command.
- The --artifacts flag was removed from the dump command.
- The sha256 attribute is now optional (although recommended!) for
remote repository rules.
- Add instrumented file provider support to Skylark rules.
- Add imports attribute to native Python rules.
- Allow overriding -gsplit-dwarf from copts.
- Improved sandbox performance on XFS filesystems.
| commit | 850fe1b13ec470bac7a5b48ad338b2f2700ce2f5 | [log] [tgz] |
|---|---|---|
| author | Dmitry Lomov <dslomov@google.com> | Tue Jul 12 13:48:28 2016 +0200 |
| committer | Dmitry Lomov <dslomov@google.com> | Tue Jul 12 13:48:28 2016 +0200 |
| tree | f23578a17e1d3a3a93f7c4bfe2b989420be566b4 | |
| parent | 581c0a04f5b5d8269b2ca08fd5d3f6f9789ef7cf [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.