Please update the description to say what can now use target and exec constraints, I was very confused until I read the code.

I was looking at the commit that changed exec_compatible_with to target_compatible_with and I wonder if we need to change the usages back to exec_compatible_with in the jdk workspace template. WDYT?

The setup that failed for us is this:

• we build on a Linux-x86_64 machine. Our JDK is setup using remote_java_repository.
• we are building an Android app with C++ library.
• for each android CPU type, we have a different platform.

Our JDKs are with these compatible_with:

• Linux: ["@platforms//os:linux", "@platforms//cpu:x86_64"]
• mac Intel: ["@platforms//os:macos", "@platforms//cpu:x86_64"]
• mac Apple Silicon: ["@platforms//os:macos", "@platforms//cpu:aarch64"]
• Windows: ["@platforms//os:windows", "@platforms//cpu:x86_64"]

Our command line to build the app with arm64 variant will look something like this:

bazelisk build //src/main/java/com/app:app --platforms=@client-core//other/bazel/platform:android-arm64

This will fail with bazel 6.2 since our JDKs are not target compatible with the specified platforms argument.

Switching from target_compatible_with to exec_compatible_with solves our problem. My rationale was that the Java compiler produces byte-code artifacts that are cross-platform, but the binaries in the JDK package are specified to the host (exec).

The file changed here have been moved out of bazel and now resides in @rules_java. If this is still an issue with Bazel 7, please consider opening a PR in that repo.