A test case for grpc-netty-shaded version agreement

[suztomo]

Example googleapis/java-spanner#1553

Failed to execute goal on project spanner-snapshot: Could not resolve dependencies for project com.google.cloud:spanner-snapshot:jar:1.0.23:
Failed to collect dependencies for com.google.cloud:spanner-snapshot:jar:1.0.23:
...
com.google.cloud:google-cloud-spanner:jar:6.15.3-SNAPSHOT -> com.google.api:gax-grpc:jar:2.7.0 -> io.grpc:grpc-xds:jar:1.41.0 -> io.grpc:grpc-netty-shaded:jar:[1.41.0,1.41.0],
com.google.cloud:google-cloud-spanner:jar:6.15.3-SNAPSHOT -> io.grpc:grpc-alts:jar:1.42.1 -> io.grpc:grpc-netty-shaded:jar:[1.42.1,1.42.1],

A canary project that declares both com.google.api:gax-grpc and io.grpc:grpc-alts using the version of this shared dependencies BOM should be able to build.

Tricky part is that if the canary project imports the shared dependencies BOM, then Maven controls the transitive dependency and thus it just succeeds. Maybe a multi-module project would be the solution.

[suztomo]

The same problem recurred in Beam 2.36 release candidate.

apache/beam#16672

The problematic ones are the following two that forces conflicting version for grpc-netty-shaded.

• org.apache.beam:beam-sdks-java-io-google-cloud-platform:jar:2.36.0 -> com.google.api:gax-grpc:jar:2.8.1 -> io.grpc:grpc-xds:jar:1.42.1 -> io.grpc:grpc-netty-shaded:jar:[1.42.1,1.42.1]
• org.apache.beam:beam-sdks-java-io-google-cloud-platform:jar:2.36.0 -> io.grpc:grpc-alts:jar:1.43.2 -> io.grpc:grpc-netty-shaded:jar:[1.43.2,1.43.2]

I think the logic would be for each member of the shared dependencies BOM, we should have exactly one gRPC version among them (including the gRPC artifacts themselves).

• This is GAX's gRPC version https://github.com/googleapis/gax-java/blob/master/dependencies.properties#L28
• This is the shared dependencies BOM's gRPC version https://github.com/googleapis/java-shared-dependencies/blob/main/first-party-dependencies/pom.xml#L58