| commit | b1376ddb00e54b7c381c43fc74dc7c269cb8d057 | [log] [tgz] |
|---|---|---|
| author | Googler <hvd@google.com> | Tue Nov 04 11:14:52 2025 -0800 |
| committer | rules_java Copybara <noreply@google.com> | Tue Nov 04 11:15:24 2025 -0800 |
| tree | e1b1ec3ef279d9bb42c2e5faa53ecafeabc50961 | |
| parent | 8bf8a941c42906219e93fc678ebbfcbe7c38bdef [diff] |
Add support for an unstripped bootclasspath Running the bootclasspath through ijar was added in https://github.com/bazelbuild/rules_java/pull/324 and was always enabled. This change lets us selectively disable it. This ensures we don't end up depending on the prebuilt ijar in the non-prebuilt toolchain case. This is also needed to bootstrap bazel where we don't have access to `@remote_java_tools` PiperOrigin-RevId: 828056087 Change-Id: I38402112139221cea606b64110fb1854795a8113
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