grpc-java/core
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 core: Remove useless ExperimentalApi annotation from pick first 2024-03-28 08:07:53 -07:00
BUILD.bazel bazel: Use the `artifact` macro for loading maven deps 2024-03-28 14:33:32 -07:00
build.gradle Remove semi-circular dependency between core and util 2024-02-16 12:31:54 -08:00