| commit | 9b84026b40dfdba5e57db814dc70793fca0e66cc | [log] [tgz] |
|---|---|---|
| author | Googler <hvd@google.com> | Wed Nov 05 03:25:26 2025 -0800 |
| committer | rules_java Copybara <noreply@google.com> | Wed Nov 05 03:25:57 2025 -0800 |
| tree | fd32e549536363ff8f6ff1013aa393df6af638db | |
| parent | 56177d044e0d4e193c14549dd1d0c0c0c78f3f01 [diff] |
Rename target to avoid artifact conflict
The `bootclasspath` rule internally generates a (intermediate) `{name}_unstripped.jar` artifact which conflicts with the output of the `//toolchains:platformclasspath_unstripped` target
(ignore-relnotes)
PiperOrigin-RevId: 828390314
Change-Id: I3a5a21a52c6697c1497db295277a2c96c52df5a9
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