| commit | aef7514ad80ae6b7c366b7b72dfde40f366498cb | [log] [tgz] |
|---|---|---|
| author | Googler <cushon@google.com> | Mon Mar 10 14:17:16 2025 -0700 |
| committer | rules_java Copybara <noreply@google.com> | Mon Mar 10 14:17:50 2025 -0700 |
| tree | 906ca9a74c541a20a5d8203ebd280258536b83d1 | |
| parent | d649cd8dc67d26904f8d884e9b0f4abd70fedfc1 [diff] |
Add java_library outputs to validation outputs This ensures that compilation actions are performed for libraries that are only used as neverlink dependencies, to ensure that any compilation errors are reported. The minimize the number of additional validation actions, the validation is done for targets that set neverlink, and their transitive runtime dependencies, so anything that is used as a transitive neverlink dep is covered. PiperOrigin-RevId: 735509081 Change-Id: I76b30e68c8b37eca165861e893ec595cb3040d6c
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