| commit | 2e7fb93b9d82c548881af219d6e2c1a3c1b7725f | [log] [tgz] |
|---|---|---|
| author | Jordan <jordan.mele@outlook.com.au> | Wed Oct 19 05:19:51 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Oct 19 05:22:06 2022 -0700 |
| tree | 079a1ebfa5f84da0e78e18c759454e56d438b53e | |
| parent | b927d81ea4bb9d2b99f23109d66454e108914cb8 [diff] |
Removed documentation for `-extra_checks` which has been gone since v3.5 Support for flag removed in 1819f6ecf5b7f28fadcff54dd9454a91d9d2d8a6 Closest analogue is `-XepDisableAllChecks`, an Error Prone flag documented at https://errorprone.info/docs/flags Note that `-XepDisableAllChecks` will not necessarily disable all Error Prone checks. For example, [UnicodeDirectionalityCharacters](https://github.com/google/error-prone/blob/0da434efc8adca8682bea159c97f7fab65745c83/core/src/main/java/com/google/errorprone/bugpatterns/UnicodeDirectionalityCharacters.java) cannot be disabled. Closes #15899. PiperOrigin-RevId: 482176108 Change-Id: Iba5a1edb67ded4b10ab819a6e83a2a66c1989be2
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only 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:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
