| commit | be0f07eeeba1d07c69e3138096c3f82e4d921757 | [log] [tgz] |
|---|---|---|
| author | Ivo List <ilist@google.com> | Wed Oct 07 12:14:13 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Oct 07 12:15:13 2020 -0700 |
| tree | 785a7d22e1b7aba307e4f21994f03109235efe46 | |
| parent | 9b82aebfb9fb0502d5a256427adcb23f328ed426 [diff] |
Move default_java_toolchain definitions into java_tools repository default_java_toolchain macro is handy to define toolchains in //tools/jvm/BUILD without making a release of java_tools. However default_java_toolchain heavily relies on selects by operating system to pick the right parts from the right java_tools. This indirection is removed by putting definition directly into java_tools. This is the first part. After java_tools release, default_java_toolchain and remote_java_tools_java_import can be removed. Closes #12224. PiperOrigin-RevId: 335923902
{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
