@@ -68,17 +68,6 @@ filegroup(
6868# TODO: migrate away from using @bazel_tools//tools/jdk:bootstrap_runtime_toolchain_type ?
6969# toolchain_type(name = "bootstrap_runtime_toolchain_type")
7070
71- # The Java runtime to extract the bootclasspath from that is then used to compile Java sources.
72- #
73- # As the bootclasspath is platform independent, toolchains of this type may have no constraints.
74- # Purely as an optimization to prevent unnecessary fetches of remote runtimes for other
75- # architectures, toolchains of this type may have constraints on the execution platform that match
76- # those on the corresponding compilation toolchain.
77- #
78- # Toolchains of this type are only consumed internally by the bootclasspath rule and should not be
79- # accessed from Starlark.
80- # toolchain_type(name = "bootstrap_runtime_toolchain_type")
81-
8271# Points to toolchain[":runtime_toolchain_type"] (was :legacy_current_java_runtime)
8372java_runtime_alias (name = "current_java_runtime" )
8473
@@ -179,9 +168,6 @@ cc_library(
179168 ]
180169]
181170
182- # On Windows, executables end in ".exe", but the label we reach it through
183- # must be platform-independent. Thus, we create a little filegroup that
184- # contains the appropriate platform-dependent file.
185171alias (
186172name = "ijar" ,
187173actual = ":ijar_prebuilt_binary_or_cc_binary" ,
@@ -208,12 +194,6 @@ alias(
208194 }),
209195)
210196
211- # On Windows, Java implementation of singlejar is used. We create a little
212- # filegroup that contains the appropriate platform-dependent file.
213- # Once https://github.com/bazelbuild/bazel/issues/2241 is fixed (that is,
214- # the native singlejar is used on windows), this file group can be reused since
215- # on Windows, executables end in ".exe", but the label we reach it through
216- # must be platform-independent.
217197alias (
218198name = "singlejar" ,
219199actual = ":singlejar_prebuilt_or_cc_binary" ,