| commit | f44bc4732650f6ad011407cc5c41cb36de23acdb | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Wed May 01 17:41:23 2019 -0400 |
| committer | Danna Kelmer <dannark@google.com> | Wed May 01 17:41:23 2019 -0400 |
| tree | 346a2506e3e3480329f82725f7eb2ca09b48eb77 | |
| parent | e72a5c6624a15a6b98c69dfa6069a051bd409ad4 [diff] |
Release 0.25.0 (2019-05-01)
Baseline: 03662462941953dad23af88693804b8b1d4430b9
Cherry picks:
+ 3f7f255f9a8345b8898e3953e7e53d68106cc63d:
Windows: fix native test wrapper's arg. escaping
+ afeb8d0b7fef619159fc8fbaaeb8bd41dd2619bd:
Flip --incompatible_windows_escape_jvm_flags
+ 4299b6549cbc1b3e4494c91ed2f51d49b14c7980:
Sort DirectoryNode children to ensure validity.
+ 231270c67d5aa771462245531fa9b2ee7d3d0ae8:
Conditionally use deprecated signature for initWithContentsOfURL
+ 75a3a531b08e727ade4fa3cb0a574bd142727cce:
Add http_archive entries for testing with various JDK versions.
+ 4a6354a3a5ca23583f8b62e3e439a04ce75b863f:
Now that ubuntu1804 uses JDK 11, remove explicit
ubuntu1804_java11 tests.
+ ae102fbde3c1ff87e4f67007a275fb30792a4e8d:
Fix wrong name of ubuntu1804_javabase9 task.
+ 0020a97fdc20ca099ec6386771b20d3236f9890d:
Remove @executable_path/Frameworks from rpaths
+ 130f86ded1ce84f959f0b78c065211902faed546:
Download stderr/stdout to a temporary FileOutErr
Incompatible changes:
- (Starlark rules) The legacy "py" provider can no longer be passed
to or produced by native Python rules; use
[PyInfo](https://docs.bazel.build/versions/master/skylark/lib/PyIn
fo.html) instead. See
[#7298](https://github.com/bazelbuild/bazel/issues/7298) for more
information.
- (Python rules) The `default_python_version` attribute of the
`py_binary` and `py_test` rules has been renamed to
`python_version`. Also, the `--force_python` flag has been
renamed to `--python_version`. See
[#7308](https://github.com/bazelbuild/bazel/issues/7308) for more
information.
- (Python rules) The python version now changes to whatever version
is specified in a `py_binary` or `py_test`'s `python_version`
attribute, instead of being forced to the value set by a command
line flag. You can temporarily revert this change with
`--incompatible_allow_python_version_transitions=false`. See
[#7307](https://github.com/bazelbuild/bazel/issues/7307) for more
information.
- --incompatible_disable_third_party_license_checking` is enabled
by default
- Introduced --incompatible_use_python_toolchains, which supersedes
--python_top/--python_path. See #7899 and #7375 for more
information.
- Python 3 is now the default Python version (for `py_binary` and
`py_test` targets that don't specify the `python_version`
attribute). Targets that are built for Python 3 will no longer
have their output put in a separate `-py3` directory; instead
there is now a separate `-py2` directory for Python 2 targets.
See #7359 and #7593 for more information.
- objc_library resource attributes are now disabled by default.
Please migrate them to data instead. See
https://github.com/bazelbuild/bazel/issues/7594 for more info.
- Flip --incompatible_windows_escape_jvm_flags to true. See
https://github.com/bazelbuild/bazel/issues/7486
New features:
- genrules now support a $(RULEDIR) variable that resolves to the
directory where the outputs of the rule are put.
- Added --incompatible_windows_native_test_wrapper flag: enables
using the Bash-less test wrapper on Windows. (No-op on other
platforms.)
Important changes:
- incompatible_use_jdk11_as_host_javabase: makes JDK 11 the default
--host_javabase for remote jdk
(https://github.com/bazelbuild/bazel/issues/7219)
- Makes genquery somepath output deterministic.
- Tristate attributes of native rules now reject True/False (use
1/0)
- Rollback of "Tristate attributes of native rules now reject
True/False (use 1/0)"
- Tristate attributes of native rules now reject True/False (use
1/0)
- Added -incompatible_do_not_split_linking_cmdline flag. See #7670
- Tristate attributes of native rules now temporarily accept
True/False again
- `--incompatible_disable_legacy_crosstool_fields` has been flipped
(https://github.com/bazelbuild/bazel/issues/6861)
`--incompatible_disable_expand_if_all_available_in_flag_set` has
been flipped (https://github.com/bazelbuild/bazel/issues/7008)
- `--incompatible_disable_legacy_crosstool_fields` has been flipped
(https://github.com/bazelbuild/bazel/issues/6861)
`--incompatible_disable_expand_if_all_available_in_flag_set...
RELNOTES: None.
- --incompatible_no_transitive_loads is enabled by default.
- Makes TreeArtifact deterministic.
- --incompatible_no_transitive_loads is enabled by default.
- Android NDK C++ toolchain is now configured in Starlark. This
should be a backwards compatible change, but in case of bugs
blame unknown commit.
- `--incompatible_disable_legacy_crosstool_fields` has been flipped
(https://github.com/bazelbuild/bazel/issues/6861)
`--incompatible_disable_expand_if_all_available_in_flag_set` has
been flipped (https://github.com/bazelbuild/bazel/issues/7008)
- --incompatible_no_transitive_loads is enabled by default.
- --incompatible_bzl_disallow_load_after_statement is enabled
- Added `--incompatible_require_ctx_in_configure_features`, see
https://github.com/bazelbuild/bazel/issues/7793 for details.
- Flag --incompatible_merge_genfiles_directory is flipped. This
removes the directory `bazel-genfiles` in favor of `bazel-bin`.
- previously deprecated flag --experimental_remote_spawn_cache was
removed
- `--incompatible_disallow_load_labels_to_cross_package_boundaries`
is enabled by default
- Fix an issue where the Android resource processor did not surface
errors from aapt2 compile and link actions.
- --incompatible_no_attr_license is enabled by default
- `--incompatible_disable_crosstool_file` has been flipped
(https://github.com/bazelbuild/bazel/issues/7320)
- A new flag `--incompatible_string_join_requires_strings` is
introduced. The sequence argument of `string.join` must contain
only string elements.
- --incompatible_symlinked_sandbox_expands_tree_artifacts_in_runfile
s_tree has been flipped
- Incompatible flag `--incompatible_disable_legacy_cc_provider` has
been flipped (see https://github.com/bazelbuild/bazel/issues/7036
for details).
- Don't drop the analysis cache when the same --define flag is set
multiple times and the last value is the same (e.g. if the
current invocation was run with "--define foo=bar" and the
previous one was run with "--define foo=baz --define foo=bar").
- The --incompatible_disable_genrule_cc_toolchain_dependency flag
has been flipped (see
https://github.com/bazelbuild/bazel/issues/6867 for details).
- Incompatible change
`--incompatible_remove_cpu_and_compiler_attributes_from_cc_toolcha
in` has been flipped (see
https://github.com/bazelbuild/bazel/issues/7075 for details).
- --noexperimental_java_coverage is a no-op flag.
- --experimental_java_coverage/--incompatible_java_coverage flag was
removed. See #7425.
- incompatible_use_toolchain_providers_in_java_common: pass
JavaToolchainInfo and JavaRuntimeInfo providers to java_common
APIs instead of configured targets
(https://github.com/bazelbuild/bazel/issues/7186.)
- --incompatible_remote_symlinks has been flipped. The remote
caching and execution protocol will now represent symlinks in
outputs as such. See
https://github.com/bazelbuild/bazel/issues/7917 for more details.
- Bazel is now ~20MiB smaller, from unbundling the Android rules'
runtime dependencies.
This release contains contributions from many people at Google, as well as Andreas Herrmann, Andrew Suffield, Andy Scott, Benjamin Peterson, Ed Baunton, George Gensure, Ian McGinnis, Ity Kaul, Jingwen Chen, John Millikin, Keith Smiley, Marwan Tammam, Mike Fourie, Oscar Bonilla, perwestling, petros, Robert Sayre, Ryan Beasley, silvergasp, Stanimir Mladenov, Travis Cline, Vladimir Chebotarev, ??.
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.