| commit | 1bb1b52c9d452afccbf7ce046f4133b52d6cebf8 | [log] [tgz] |
|---|---|---|
| author | Tony Aiuto <aiuto@google.com> | Wed Jan 13 10:39:41 2021 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jan 13 10:40:57 2021 -0800 |
| tree | 611cd5f970b66fbbdc39a15b113688339c867d5b | |
| parent | eb762d4e7431637e607146b1c191485795047ef9 [diff] |
Generate src/test/shell/bazel/testdata/jdk_http_archive Start generating src/test/shell/bazel/testdata/jdk_http_archive instead of it being static. This allows us to update various Java dependencies without having to manually keep WORKSPACE, jdk_http_archive and ./src/main/java/com/google/devtools/build/lib/bazel/rules/java/jdk.WORKSPACE in sync. Question for the reviewer: As this change stands now, the remote tools will have a secondary URL from github. Before, there was only the bazel mirror. E.g. ``` < urls = ["https://mirror.bazel.build/bazel_java_tools/releases/java/v11.0/java_tools-v11.0.zip", "https://github.com/bazelbuild/java_tools/releases/download/java_v11.0/java_tools-v11.0.zip"], --- > urls = [ > "https://mirror.bazel.build/bazel_java_tools/releases/java/v11.0/java_tools-v11.0.zip", > ], ``` I do not know if this is a good change or a bad one. The JDKs all have 2 URLs, one from mirror and one from azul.com. Having remote tools only from the mirror seems insufficient. It would be easy to add a feature filter URLs, but I don't want to build that if we don't really need it. Closes #12817. PiperOrigin-RevId: 351617501
{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
