rules_java not respecting --tool_java_language_version/--tool_java_runtime_version for test_jar's as of at least 7.1.0 about rules_java HOT 2 OPEN

minimum-project.zip

Attached is a minimum sample project to recreate the issue.

If you attempt to build the project you should get an error somewhere along the lines of:

ERROR: /home/cjohnstoniv/helm-farm/sample-java/BUILD:6:10: Building test-unit.jar (1 source file) failed: (Exit 1): java failed: error executing Javac command (from target //:test-unit) external/rules_java~7.1.0~toolchains~remotejdk21_linux/bin/java '--add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED' ... (remaining 19 arguments skipped)
src/test/java/hello/TestTest.java:10: error: ';' expected
        Fail me
               ^

The key piece of the error message is the: external/rules_java7.1.0toolchains~remotejdk21_linux/bin/java

I would expect this to be remotejdk11 based on the .bazelrc file.

from rules_java.

This has come up before in #148 and bazelbuild/bazel#19934

The behavior changed in bazelbuild/bazel@37eb1d7 during platformization of the java rules. From what I've gathered, the motivation for fixing the java_runtime version was to avoid issues in the default case, i.e. when a local jdk is in use. cc @comius to correct me / add more colour.

As explained in bazelbuild/bazel#19934 (comment) using a newer runtime shouldn't matter in practice, as we still correctly use the source/target language level. If you must use a specific runtime version, please declare a custom default_java_toolchain specifying the needed value for java_runtime.

from rules_java.