Split tools/jdk/BUILD into part that's needed to produce @build_tools and the content of it. There are two versions of Bazel tools available during compilation @bazel_tools//tools and @io_bazel//tools. They are used in two different ways: - the actual targets are needed - source files are needed to create and embed a new version of @bazel_tools Before the split //tools/jdk/BUILD file was used in both ways, even though it is only needed because of sources. Having everything in a single file caused evaluation by the compiling bazel. As a consequence it failed on targets/attributes that are not yet supported by it. Splitting it into two files keeps BUILD.tools unevaluated and we can use unreleased features in it. Closes #12603. PiperOrigin-RevId: 345420984
{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:
See CONTRIBUTING.md
