Remove ijar from the bazel binary.
Bazel now doesn't embed ijar anymore and uses ijar embeded in the Java tools remote repository.
Bazel embedded both ijar's source code (required by remote execution) and platform specific pre-built binaries. This change adds platform specific remote Java tools repository that include the corresponding pre-built ijar binary (for Windows, Darwin and Linux), alongside ijar's source code.
This change introduces a collection of macros that wrap the native rules `filegroup` and `java_import` and select a given target from the external java tools repository based on the current platform.
Progress on #6316.
Closes #7665.
PiperOrigin-RevId: 238613298
diff --git a/tools/jdk/BUILD.java_langtools b/tools/jdk/BUILD.java_langtools
new file mode 100644
index 0000000..0020800
--- /dev/null
+++ b/tools/jdk/BUILD.java_langtools
@@ -0,0 +1,24 @@
+package(default_visibility = ["//visibility:public"])
+
+licenses(["notice"]) # Apache 2.0
+
+load(
+ "//tools/jdk:remote_java_tools_aliases.bzl",
+ "remote_java_tools_filegroup",
+)
+
+
+remote_java_tools_filegroup(
+ name = "javac_jar",
+ target = ":java_tools/javac-9+181-r4173-1.jar",
+)
+
+remote_java_tools_filegroup(
+ name = "jdk_compiler_jar",
+ target = ":java_tools/jdk_compiler.jar",
+)
+
+remote_java_tools_filegroup(
+ name = "java_compiler_jar",
+ target = ":java_tools/java_compiler.jar",
+)
