| commit | ae8a5b22648f3e6c8a4bc58ec0bb9f7c3f1a9668 | [log] [tgz] |
|---|---|---|
| author | Googler <cushon@google.com> | Wed May 28 19:09:52 2025 -0700 |
| committer | rules_java Copybara <noreply@google.com> | Wed May 28 19:10:32 2025 -0700 |
| tree | d5b62321f67c23d8da360c53dae00efbb4f2a2ca | |
| parent | 899c2b75bdce62dbec082a3ad664f9f0b5f6ede9 [diff] |
Initial support for header compilation direct deps This adds a new output to header compilation actions which is used as the classpath for downstream header compilations, instead of using the same output for downstream header and regular compilations. Using a separate output allows trimming information that isn't needed by header compilation, but is required for regular compilation, including methods. This results in a smaller cache key for header compilation actions. PiperOrigin-RevId: 764512852 Change-Id: I4895e47f3418e9cbf602edd11fde38de5f3e32ca
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