commit c3e6caceec3b6f9550021fb11f3932369d7164bd
author Fabian Meumertzheim <fabian@meumertzhe.im> Tue Oct 17 09:40:10 2023 +0200
committer Fabian Meumertzheim <fabian@meumertzhe.im> Tue Oct 17 09:40:10 2023 +0200
tree f7bdeed4083ef53d30a9fbcb5a0c7eca1eacd571
parent 0cdcecb2ee3a1da92f95ba0af036f20fa4179fb5

Revert "Reference `platformclasspath` in `@bazel_tools`"

This reverts commit 54e89daeacd9728f45b4c16b3834e16d5f40e11c.

Going through `@bazel_tools` to reference the bootstrap classpath is no
longer needed with Bazel 7, which always uses toolchain macros that
define the required bootstrap runtime toolchains.

Since the original problem didn't arise with Bzlmod, where the Java
toolchains have always come from rules_java rather than bazel_tools,
this fixes https://github.com/bazelbuild/bazel/issues/19837 for Bazel
itself by allowing it to use the new bootstrap classpath rule while
still being built with Bazel 6.4.0.