Add `load()` statements for the Bazel builtin top-level java symbols
Loads are being added in preparation for moving the symbols out of Bazel and into `rules_java`. PiperOrigin-RevId: 625688195pull/16474/head
parent
1a7ea70730
commit
c755d9ac1a
|
@ -16,7 +16,7 @@ bazel_dep(name = "abseil-cpp", repo_name = "com_google_absl", version = "2023080
|
|||
bazel_dep(name = "bazel_skylib", version = "1.4.1")
|
||||
bazel_dep(name = "jsoncpp", version = "1.9.5")
|
||||
bazel_dep(name = "rules_cc", version = "0.0.9")
|
||||
bazel_dep(name = "rules_java", version = "4.0.0")
|
||||
bazel_dep(name = "rules_java", version = "5.3.5")
|
||||
bazel_dep(name = "rules_jvm_external", version = "5.1")
|
||||
bazel_dep(name = "rules_pkg", version = "0.7.0")
|
||||
bazel_dep(name = "rules_python", version = "0.10.2")
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
""" Custom rule to generate OSGi Manifest """
|
||||
|
||||
load("@rules_java//java:defs.bzl", "java_library")
|
||||
load("@rules_java//java:defs.bzl", "JavaInfo", "java_library")
|
||||
|
||||
# Note that this rule is currently agnostic of protobuf concerns and could be
|
||||
# pulled out as a general purpose helper to allow migrations from maven to bazel
|
||||
|
|
Loading…
Reference in New Issue