| commit | 8bf8bcaca17fc15ba4fff3229d4eead4b653214a | [log] [tgz] |
|---|---|---|
| author | Googler <hvd@google.com> | Mon Dec 01 03:55:59 2025 -0800 |
| committer | rules_java Copybara <noreply@google.com> | Mon Dec 01 03:56:33 2025 -0800 |
| tree | e4e68725bc8e2c12cb55ad77c19d66362d399232 | |
| parent | b6856588ba834750a1e66b2dd1b274a1f09f66a5 [diff] |
Extract utility methods used in the loading phase from `impl/java_helper.bzl` into a separate bzl file Methods used only by a single other load-affecting bzl file are inlined there instead. This way `impl/java_helper.bzl` is only loaded from bzl files used during rule implementations and should not be needed for the loading-phase, so making changes to this file don't invalidate the results of `blaze query`[^1]. PiperOrigin-RevId: 838701557 Change-Id: If462c46b1b8f2e5be12322a8af7d1a27e392bdfd
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