Update rules_jvm_external 6.3 -> 6.5

[jin]

Fixes java_export loading with RJE and Bazel 8.

with 6.3:

$ USE_BAZEL_VERSION=8.0.0rc2 bazelisk query //java/core:core_mvn-lib --enable_bzlmod
ERROR: /usr/local/google/home/jingwen/code/protobuf/java/core/BUILD.bazel:169:21: //java/core:lite_mvn-lib: no such attribute 'javacopts' in 'java_library' rule
ERROR: /usr/local/google/home/jingwen/code/protobuf/java/core/BUILD.bazel:169:21: //java/core:lite_mvn-lib: no such attribute 'resources' in 'java_library' rule (did you mean 'features'?)
ERROR: /usr/local/google/home/jingwen/code/protobuf/java/core/BUILD.bazel:169:21: //java/core:lite_mvn-lib: no such attribute 'runtime_deps' in 'java_library' rule
ERROR: /usr/local/google/home/jingwen/code/protobuf/java/core/BUILD.bazel:291:21: //java/core:core_mvn-lib: no such attribute 'javacopts' in 'java_library' rule
ERROR: /usr/local/google/home/jingwen/code/protobuf/java/core/BUILD.bazel:291:21: //java/core:core_mvn-lib: no such attribute 'resources' in 'java_library' rule (did you mean 'features'?)
ERROR: /usr/local/google/home/jingwen/code/protobuf/java/core/BUILD.bazel:291:21: //java/core:core_mvn-lib: no such attribute 'runtime_deps' in 'java_library' rule
ERROR: Evaluation of query "//java/core:core_mvn-lib" failed

with 6.5:

$ USE_BAZEL_VERSION=8.0.0rc2 bazelisk query //java/core:core_mvn-lib --enable_bzlmod
WARNING: For repository 'bazel_skylib', the root module requires module version bazel_skylib@1.7.0, but got bazel_skylib@1.7.1 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'rules_java', the root module requires module version rules_java@7.12.2, but got rules_java@8.2.0 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'rules_python', the root module requires module version rules_python@0.28.0, but got rules_python@0.36.0 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'platforms', the root module requires module version platforms@0.0.8, but got platforms@0.0.10 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'zlib', the root module requires module version zlib@1.3.1, but got zlib@1.3.1.bcr.3 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'proto_bazel_features', the root module requires module version bazel_features@1.17.0, but got bazel_features@1.18.0 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'com_google_googletest', the root module requires module version googletest@1.14.0, but got googletest@1.15.2 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'rules_proto', the root module requires module version rules_proto@4.0.0, but got rules_proto@6.0.2 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
//java/core:core_mvn-lib

Note that build still doesn't work with a different failure mode:

$ USE_BAZEL_VERSION=8.0.0rc2 bazelisk build //java/core:core_mvn --enable_bzlmod
ERROR: no such package '@@protobuf+//': The repository '@@protobuf+' could not be resolved: Repository '@@protobuf+' is not defined
ERROR: /usr/local/google/home/jingwen/code/protobuf/java/core/BUILD.bazel:187:14: every rule of type proto_library implicitly depends upon the target '@@protobuf+//:protoc', but this target could not be found because of: no such package '@@protobuf+//': The repository '@@protobuf+' could not be resolved: Repository '@@protobuf+' is not defined
ERROR: Analysis of target '//java/core:core_mvn' failed; build aborted: Analysis failed
INFO: Elapsed time: 12.522s, Critical Path: 0.04s
INFO: 1 process: 1 internal.
ERROR: Build did NOT complete successfully
FAILED:
    Fetching repository @@rules_java++toolchains+remote_java_tools; starting

This should also be cherrypicked into 29.x.

[zhangskz]

@jin Thanks Jin! FYI, you can send these to us directly as internal CL's for main instead which should help with running tests and landing these faster. these changes get imported from Github anyways.

[zhangskz]

IIRC, we're also waiting on rules_jvm_external 6.6. Is there any value / does this help unblock Bazel 8 to backporting this to 29.x ahead of those addl. fixes?

[jin]

Is there any value / does this help unblock Bazel 8 to backporting this to 29.x ahead of those addl. fixes?

Yes, it unblocks Bazel 8, at least it fixes this issue incrementally by picking up bazel-contrib/rules_jvm_external#1273.

rules_jvm_external 6.6

Can you confirm what exactly you're waiting for in 6.6? From our end, we are aware of bazel-contrib/rules_jvm_external@3ed7d65 and our rules_android dependency bump.