Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_java/20951906fa6a74346663acc39a6fd22378128cb6
commit
20951906fa6a74346663acc39a6fd22378128cb6
[log] [tgz]
author
Googler <cpovirk@google.com>
Wed Dec 03 06:08:39 2025 -0800
committer
rules_java Copybara <noreply@google.com>
Wed Dec 03 06:09:08 2025 -0800
tree
3b3cf52385e048769a1d778afdd7ca94f2671a66
parent
dbd8cb408911b79c6d7047ac4355ff89b1b90685 [diff]
Refer to the SingleJar "executable" instead of "deploy jar."

I don't think it's been a deploy jar in any environment for a while, and whatever it is, I think we run it directly as a executable.

PiperOrigin-RevId: 839725877
Change-Id: I8d8e67b3eb7bd4af11387efb727853740370f565
1 file changed
tree: 3b3cf52385e048769a1d778afdd7ca94f2671a66
  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