Google Git
Sign in
bazel / rules_java / aa153f057a204f6212ec766029ff9df2b4c0285c
commitaa153f057a204f6212ec766029ff9df2b4c0285c[log] [tgz]
authorGoogler <hvd@google.com>Fri Nov 14 02:14:36 2025 -0800
committerrules_java Copybara <noreply@google.com>Fri Nov 14 02:15:10 2025 -0800
tree0f64e046ef5d55e77c5c4f64399ed1f025af7500
parent8427063e872aa3bddf1d091c3faa129d9395a261 [diff]
Execute the `check_remote_java_tools_configs_test` only on a single platform

The test is platform / bazel independent and is wasteful to run on all platforms / bazel combinations

(ignore-relnotes)

PiperOrigin-RevId: 832226923
Change-Id: I74ede6ccf16f8f5ec4331ee258495e386188026d
2 files changed
tree: 0f64e046ef5d55e77c5c4f64399ed1f025af7500
  1. .bazel_checkout/
  2. .bazelci/
  3. .bcr/
  4. .github/
  5. distro/
  6. examples/
  7. java/
  8. test/
  9. third_party/
  10. toolchains/
  11. .bazelignore
  12. .bazelrc
  13. .gitignore
  14. AUTHORS
  15. BUILD
  16. CODEOWNERS
  17. CONTRIBUTING.md
  18. LICENSE
  19. MODULE.bazel
  20. README.md
  21. renovate.json
  22. WORKSPACE
  23. WORKSPACE.bzlmod
README.md

rules_java

  • Postsubmit Build status
  • Postsubmit + Current Bazel Incompatible Flags Build status

Java Rules for Bazel https://bazel.build.

Documentation

For a quickstart tutorial, see https://bazel.build/start/java

For slightly more advanced usage, like setting up toolchains or writing your own java-like rules, see https://bazel.build/docs/bazel-and-java

Core Java rules

Add a load like:

load("@rules_java//java:java_library.bzl", "java_library")

to your BUILD / BUILD.bazel / bzl` files

For detailed docs on the core rules, see https://bazel.build/reference/be/java