Doing so will help validating changes to the "self-service" library generation workflow (e.g., as in #876).

Theoretically, we should be able to generate some libraries against actual API service protos like the following (may need to change a few things in WORKSPACE or some BUILD files).

bazel build @com_google_googleapis//google/cloud/compute/v1:google-cloud-compute-v1-java

Then unpack bazel-bin/external/com_google_googleapis/google/cloud/compute/v1/google-cloud-compute-v1-java.tar.gz and run ./gradlew clean check publishToMavenLocal at the root of the generated library.

compute is REST and all others are gRPC at the moment, so compute and another library are good candidates.