James Ward

Dug in again and I am using `DockerContainer` and still need some more docs :) For instance, I'm not sure how to wait until a port is listening.

Yeah, on my other related projects I use: ``` Wait.forHttp("/") ``` Thanks!

I think this means we will see a linuxX64 target which I'd love to have especially for the IO / Compression stuff.

I believe that you can have dependencies on libraries that contain protos and the wrappers (Kotlin Protos for example) will be created around them. So I think this should work....

Here is the sample: https://github.com/jamesward/grpc-kotlin-sample-deps Date Kotlin Builders part: https://github.com/jamesward/grpc-kotlin-sample-deps/blob/main/src/main/kotlin/io/grpc/examples/helloworld/HelloWorldServer.kt#L55-L60 The trick is to add a dep to the `protobuf` configuration, like: ``` protobuf("com.google.api.grpc:proto-google-common-protos:2.11.0") ``` That causes the protobuf Gradle...

Check out how we do this in the grpc-kotlin examples: https://github.com/grpc/grpc-kotlin/tree/master/examples protos module: https://github.com/grpc/grpc-kotlin/blob/master/examples/protos/build.gradle.kts primary stub module: https://github.com/grpc/grpc-kotlin/blob/master/examples/stub/build.gradle.kts Let me know if that helps.

The structure overview is something like: - `protos` module contains protos - `stub` module depends on protos & other library via `protobuf(project(":protos"))` and generates sources & compiles classes - `server`...

The one part that might be hard to setup is a dependency in `protos` on the other library since that project doesn't have the `protobuf` configuration. Probably a way to...

I have it setup so that `stub` generates the proto messages and the gRPC wrappers. But you could definitely split that out into two separate modules. I don't think there...

Yeah I agree. For now, here is a more minimal example that might help: https://github.com/GoogleCloudPlatform/kotlin-samples/tree/main/run/grpc-hello-world-gradle