remotely-built java_binarys can't run locally

[kevingessner]

Description of the problem / feature request:

java_binary targets that are built with remote execution can't run locally, because the wrapper script has the wrong path to java.

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Create a straightforward java_binary with some deps, e.g.

java_binary(
    name = "foo",
    main_class = "my.foo",
    runtime_deps = [
        "//my/foo",
        "//third_party/jvm/org/apache/logging/log4j:log4j_core",
    ],
)

Build it with the a remote execution config using rbe_autoconfig from Bazel toolchains 0.29.8 and the default build container (e.g. with Google RBE).

The binary builds fine with bazel --config=remote build //:foo. However, it fails when run with bazel --config=remote run //:foo:

/home/kgessner/.cache/bazel/_bazel_kgessner/[snip]/foo: line 359: /usr/lib/jvm/java-8-openjdk-amd64/bin/java: No such file or directory

The java_binary wrapper/launcher has the wrong java path: /usr/lib/jvm/java-8-openjdk-amd64/bin/java is the path to java in the build container, but not locally.

I can't find a combination of javabase/java_toolchain that makes the wrapper include my local JDK without breaking RBE. I can work around it with --java_launcher=@bazel_tools//tools/jdk:java but that results in a deprecation warning about local_jdk, so it's not a sustainable solution.

What operating system are you running Bazel on?

centos 7

What's the output of bazel info release?

release 0.29.1

Have you found anything relevant by searching the web?

I did ask on SO: https://stackoverflow.com/questions/58348645/remotely-built-java-binarys-cant-run-locally

I found this about the local_jdk deprecation warning but those solutions aren't compatible with --java_launcher: https://stackoverflow.com/questions/53066974/how-can-i-use-the-jar-tool-with-bazel-v0-19

[evantorrie]

I too have this problem. It seems to pull the remote java toolchain's "java" path rather than using the local host.

[github-actions]

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

[github-actions]

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team (@bazelbuild/triage). Thanks!