Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_java / d4159a222e9ac0635aa3b2b39d1f0ab655846344
commitd4159a222e9ac0635aa3b2b39d1f0ab655846344[log] [tgz]
authorGoogler <hvd@google.com>Wed Nov 19 02:49:53 2025 -0800
committerrules_java Copybara <noreply@google.com>Wed Nov 19 02:50:19 2025 -0800
tree1e51a11f3c9272211bb3d16add513a2227236461
parent6ea00a46a9e5498d748d6ae843c87e21c9e8b1d9 [diff]
Fix bazel version check in `local_java_repository.bzl`

With the latest rolling release version hitting `10.x`, we can no longer rely on simple string comparision.

PiperOrigin-RevId: 834204982
Change-Id: Idb37877d983287787b6b997d4a01385164608a46
1 file changed
tree: 1e51a11f3c9272211bb3d16add513a2227236461
  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