Enable path mapping for JavaDeployJar

Enable execution_requirements = {"supports-path-mapping": "1"} on the JavaDeployJar action registration in rules_java across all deploy JARs.

Map each hermetic resource to its configuration-independent `short_path` using SingleJar's `<source_path>:<zip_path>` syntax and set `--hermetic_java_home` to `runtime.java_home_runfiles_path`. This allows path mapping to be safely enabled unconditionally across both hermetic and non-hermetic deploy JARs.

PiperOrigin-RevId: 975165217
Change-Id: I9f8544e9bc26ace4378898af6152ccbf526aaaa1
1 file changed
tree: 331a5f016cc285cf06b1983c2c3cc90153c9a716
  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

Build status

Java Rules for Bazel https://bazel.build.

Documentation

For a quickstart tutorial, see https://bazel.build/start/java

The fastest way to try this in an empty project is to click the green “Use this template” button on https://github.com/bazel-starters/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