Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_java/b07c3191fa8a0fd95bff87ab035975edfe5753a8
commit
b07c3191fa8a0fd95bff87ab035975edfe5753a8
[log] [tgz]
author
Googler <hvd@google.com>
Fri May 23 03:14:18 2025 -0700
committer
rules_java Copybara <noreply@google.com>
Fri May 23 03:15:00 2025 -0700
tree
6eab3658979537f7c8d909de6ae760617c26b27e
parent
6915f89962442c5def663f559b75a4a8c2377b1b [diff]
Use Rocky Linux instead of CentOS for rules_java BCR presubmits

See https://github.com/bazelbuild/continuous-integration/issues/2272

(ignore-relnotes)

PiperOrigin-RevId: 762345962
Change-Id: I68a6e1805418144d409d2afd1a51d77f37df40fe
1 file changed
tree: 6eab3658979537f7c8d909de6ae760617c26b27e
  1. .bazel_checkout/
  2. .bazelci/
  3. .bcr/
  4. .github/
  5. distro/
  6. examples/
  7. java/
  8. test/
  9. toolchains/
  10. .bazelignore
  11. .bazelrc
  12. .gitignore
  13. AUTHORS
  14. BUILD
  15. CODEOWNERS
  16. CONTRIBUTING.md
  17. LICENSE
  18. MODULE.bazel
  19. README.md
  20. renovate.json
  21. WORKSPACE
  22. 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