Google Git
Sign in
bazel / rules_java / 4a1933abf58755b35775e3c5d0c87da0b742771e
commit4a1933abf58755b35775e3c5d0c87da0b742771e[log] [tgz]
authorGoogler <steinman@google.com>Thu Oct 23 21:31:09 2025 -0700
committerrules_java Copybara <noreply@google.com>Thu Oct 23 21:31:47 2025 -0700
tree15de3cb52f9d2b72b7316bfe1e7fff17ad19c029
parent76212e60692337b1bb10afa98a8163279fe99e17 [diff]
Migrate swig_include_scanning to Starlark. In native code, this is hard coded to True, but it's also used in starlark code. So, in native code, remove references to the flag. In Starlark code, refer to the starlark option. No OSS code here, so we can add the extra attribute to refer to the flag.

PiperOrigin-RevId: 823331236
Change-Id: I4adc25b86c531306e9d4491b985ea95400a875c3
1 file changed
tree: 15de3cb52f9d2b72b7316bfe1e7fff17ad19c029
  1. .bazel_checkout/
  2. .bazelci/
  3. .bcr/
  4. .github/
  5. distro/
  6. examples/
  7. java/
  8. test/
  9. third_party/
  10. toolchains/
  11. .bazelignore
  12. .bazelrc
  13. .gitignore
  14. AUTHORS
  15. BUILD
  16. CODEOWNERS
  17. CONTRIBUTING.md
  18. LICENSE
  19. MODULE.bazel
  20. README.md
  21. renovate.json
  22. WORKSPACE
  23. WORKSPACE.bzlmod
README.md

rules_java

  • Postsubmit Build status
  • Postsubmit + Current Bazel Incompatible Flags Build status

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