Hey, thanks everyone for your feedback. :) I decided to move all .proto files from the service projects into a separate API project. The API project is language-agnostic but could be used for distributing language-specific generated code in the future, if this ever becomes a requirement.
The .proto files are copied from the API project into each individual service project for now. In the future I can replace manual copying with jar dependencies including only the .proto files. I still need to figure out the details how to manage changes in the .proto APIs without breaking backwards-compatibility, but protobuf seems to make this easy. Distributing generated code does not make sense for us for now, as we are a very small shop and only use Java. Thus the language-specific code is also generated in every service project. This allows me to make all service builds fully independent from each other, and I can also update grpc-java independently in each service. -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CACHcfZo%3DUBzYVDaWOOr7i%2B_xcVEquHw6nAnGqkD2LnqTVSqkjw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
