Nicolas,
Can you share details?

My team has been wrestling with gRPC proto distribution as well. Today we 
have a shared github repo with some basic CI to validate style and protect 
against breaking changes (using protolock 
<https://github.com/salesforce/proto-backwards-compat-maven-plugin>). Teams 
publish their protos when they want others to consume them by checking them 
into the repo. Consumers copy the protos into their projects manually and 
run the gRPC code generator as part of the build process.

We've gotten a lot of pushback on distribution by copy-paste. Developers 
want an artifact they can point to from their Maven poms. Publishing 
generated code as a jar artifact doesn't work because it revlocks the 
client and server to the same versions of the gRPC and protobuf libraries.

On Thursday, September 20, 2018 at 3:38:09 PM UTC-7, Nicolas Noble wrote:
>
> We definitely have some plans, yes. We're in the planning and designing 
> phase at the moment, and we'd be more than happy to hear about your 
> requirements and current pain points, in order to integrate these in our 
> plans.
>
> On Fri, Sep 14, 2018 at 12:55 PM Feng Xiao <[email protected] 
> <javascript:>> wrote:
>
>> +Nicolas Noble <javascript:> +grpc.io <javascript:> 
>>
>> On Fri, Sep 14, 2018 at 7:55 AM Mark Wardle <[email protected] 
>> <javascript:>> wrote:
>>
>>> Dear all,
>>>
>>> I have used protobuf to define interactions between golang and java 
>>> applications.
>>>
>>> It clearly makes sense to create a standalone protobuf repository 
>>> independent of the projects in which they are used.
>>>
>>> Is there a canonical way of taking a standalone protobuf repository, and 
>>> creating a build system that a) creates the artefacts for each supported 
>>> language from those protobuf/gRPC definitions b) integrates those artefacts 
>>> with other projects' build systems?
>>>
>> Nicolas from grpc team is working on exactly this.
>>  
>>
>>>
>>> At the moment, all I can see is a step to copy source code files across 
>>> the local filesystem into the respective project directories, but this 
>>> feels a bit wrong.
>>>
>>> All advice appreciated.
>>>
>>> Thanks,
>>>
>>> Mark
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Protocol Buffers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected] <javascript:>.
>>> To post to this group, send email to [email protected] 
>>> <javascript:>.
>>> Visit this group at https://groups.google.com/group/protobuf.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
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/0cfae9b6-e7d7-4714-92ef-49d3c552416c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to