Enable Bzlmod for Bazel
Bazel can now be built with Bzlmod with dependencies fetched from [the Bazel Central Registry](https://github.com/bazelbuild/bazel-central-registry) (https://github.com/bazelbuild/bazel-central-registry/issues/7).
Changes in this PR:
- Added MODULE.bazel file for Bazel
- Added MODULE.bazel file for third_party/remoteapis and third_party/googleapis to make them work as Bazel modules
- Updated gson to 2.8.6, because we build with protobuf 3.19.0 with Bzlmod which needs a newer version of gson.
- Added WORKSPACE.bzlmod, this eventually should be empty, but for now we still need some bind rules to make some jar dependencies available for protobuf.
- package-bazel.sh: use wildcard to locate the directory of the platforms repo, whose canonical repo name is `platform.<version>` when building with Bzlmod.
To build Bazel with Bzlmod:
- Copy WORKSPACE.bzlmod to WORKSPACE
- Run `USE_BAZEL_VERSION=last_green bazelisk build --experimental_enable_bzlmod //src:bazel_nojdk`
Closes #14171.
PiperOrigin-RevId: 406097216
diff --git a/WORKSPACE.oss.bzlmod b/WORKSPACE.oss.bzlmod
new file mode 100644
index 0000000..5bfcf18
--- /dev/null
+++ b/WORKSPACE.oss.bzlmod
@@ -0,0 +1,31 @@
+# Replace the original WORKSPACE file with this file to build Bazel with bzlmod.
+# We still need the bind rules to make protobuf work.
+workspace(name = "io_bazel")
+
+# Required by @com_google_protobuf//java/util:util in protobuf 3.19.0
+# TODO(pcloudy): Remove those bind rules, when com_google_protobuf can
+# fetch jar dependencies via rules_jvm_external with module extension.
+bind(
+ name = "error_prone_annotations",
+ actual = "//third_party:error_prone_annotations",
+)
+
+bind(
+ name = "j2objc_annotations",
+ actual = "//third_party/java/j2objc-annotations:j2objc-annotations",
+)
+
+bind(
+ name = "gson",
+ actual = "//third_party:gson",
+)
+
+bind(
+ name = "jsr305",
+ actual = "//third_party:jsr305",
+)
+
+bind(
+ name = "guava",
+ actual = "//third_party:guava",
+)
