Closed bob04619 closed 5 years ago
There shouldnt be any compatibility issues with the protobuf-lite runtime. To help out, I set up a protobuf-lite example configuration in the template project. If you encounter any issues please let me know.
You're right about the issue with the dependency polluting the classpath so Ill be sure to take care of that in the next release. In the mean time you can configure gradle to exclude the transitive grpc-protobuf.
dependencies {
implementation ("com.github.marcoferrer.krotoplus:kroto-plus-coroutines:$krotoplus_version"){
exclude group: 'io.grpc'
}
}
Thanks for the heads up!
Great, thanks. Our protobuf {} block for lite generation looks the exact same as what you ended up with. We'll run some client tests.
I don't quite envision how people will use your template if both the server and client use the same dependencies. e.g., For our stuff we use full io.grpc dependencies on server and *-lite on android. Also, as recommended by Google for the transport dependency we use this for Android:
implementation "io.grpc:grpc-okhttp:xxx"
and this for the server:
implementation "io.grpc:grpc-netty:xxx "
Thanks
The example templates provided werent targeting the android runtime specifically. Thats why the client and server both use io.grpc:grpc-netty
. The latest RC has removed the grpc-protobuf
dependency from the coroutine runtime, so you shouldn't need to exclude it explicitly anymore.
Hello, do you have example android project that is setup using kroto?
Hi, is the client gRPC generator suitable for Android?
I tested per example project and documentation instructions and it's leaking the full grpc-protobuf dependency on the runtime classpath.