grpc-java/googleapis
David Burns 00649913b0
bazel: Use the `artifact` macro for loading maven deps
The recommended way to load dependencies from `rules_jvm_external`
is to make use of the `@maven` workspace, and the most readable
way of doing that is to use the `artifact` macro provides.

This removes the need to generate the "compat" namespaces, which
`rules_jvm_external` provided for backwards compatibility with
older releases. This change also sets things up for supporting
`bzlmod`: this requires all workspaces accessed by a library to
be named "up front" in the `MODULE.bazel` file. This way, the
only repo that needs to be exported is `@maven`, rather than the
current huge list.
2024-03-28 14:33:32 -07:00
..
src Add check for empty addresses and if not there disable ipV6. (#10848) 2024-01-29 17:20:11 -08:00
BUILD.bazel bazel: Use the `artifact` macro for loading maven deps 2024-03-28 14:33:32 -07:00
build.gradle all: generate automatic module name in the manifest (#10413) 2023-07-25 09:00:11 -07:00