> Currently, the output build.gradle assumes that the proto/grpc classes will be in a separate package. For many APIs, it may be simpler to just bundle it all together; we should add an option to make this possible. #3153

Thar-Ngel · 2020-03-29T16:10:01Z

Currently, the output build.gradle assumes that the proto/grpc classes will be in a separate package. For many APIs, it may be simpler to just bundle it all together; we should add an option to make this possible.

Originally posted by @Thar-Ngel in #1917 (comment)

Thar-Ngel closed this as completed Mar 29, 2020

JustinBeckwith assigned Thar-Ngel Feb 2, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

> Currently, the output build.gradle assumes that the proto/grpc classes will be in a separate package. For many APIs, it may be simpler to just bundle it all together; we should add an option to make this possible. #3153

> Currently, the output build.gradle assumes that the proto/grpc classes will be in a separate package. For many APIs, it may be simpler to just bundle it all together; we should add an option to make this possible. #3153

Thar-Ngel commented Mar 29, 2020

> Currently, the output build.gradle assumes that the proto/grpc classes will be in a separate package. For many APIs, it may be simpler to just bundle it all together; we should add an option to make this possible. #3153

> Currently, the output build.gradle assumes that the proto/grpc classes will be in a separate package. For many APIs, it may be simpler to just bundle it all together; we should add an option to make this possible. #3153

Comments

Thar-Ngel commented Mar 29, 2020