Is your feature request related to a problem? Please describe.protobuf-maven-plugin does not support the --descriptor_set_in option, thus making it impossible to generate client code from an existing Proto descriptor set in cases when raw Proto definitions are not available (for example, when a third-party provides you with a descriptor set only).
Describe the solution you'd like
I suppose an additional argument could be added to the plugin: inputDescriptorSets.
Describe alternatives you've considered
Use the maven-antrun-plugin, for example, to pass the argument to the protoc explicitly. Unfortunately, that's not very convenient, because we would have to specify the path to the compiler manually and in multiple places (instead of referring to the global protocArtifact property of the protobuf-maven-plugin).
Hello :)
Is your feature request related to a problem? Please describe.
protobuf-maven-plugin
does not support the--descriptor_set_in
option, thus making it impossible to generate client code from an existing Proto descriptor set in cases when raw Proto definitions are not available (for example, when a third-party provides you with a descriptor set only).Describe the solution you'd like I suppose an additional argument could be added to the plugin:
inputDescriptorSets
.Describe alternatives you've considered Use the
maven-antrun-plugin
, for example, to pass the argument to theprotoc
explicitly. Unfortunately, that's not very convenient, because we would have to specify the path to the compiler manually and in multiple places (instead of referring to the globalprotocArtifact
property of theprotobuf-maven-plugin
).