Is there any reason you couldn't shade your own protobuf dependency (using,
say, the Maven shade plugin
<http://maven.apache.org/plugins/maven-shade-plugin/>) to allow it to
interoperate with a dependency's older version?
On Tue, Jun 17, 2014 at 1:49 PM, Sangjin Lee <sjl...@gmail.com> wrote:
> One case where generated APIs are not backward compatible:
> On Wednesday, April 16, 2014 7:22:41 PM UTC-7, Ilia Mirkin wrote:
>> On Wed, Apr 16, 2014 at 10:11 PM, Patrick Wendell <pwen...@gmail.com>
>> > Established based on what conventions?
>> On the convention of how protobuf releases have been done... Would you
>> be happier if it was protobuf2 4.0 and protobuf2 5.0?
>> > It means that if you want to write a library that uses proto-bufs you
>> > inter-operate with other libraries that also use protobufs.
>> Not ones that use protobufs compiled against a different major version
>> of the library. These come out every year or two. AFAIK this has
>> always been the case. (You can avoid this problem by just building the
>> proto as part of the build process rather than shipping the generated
>> files. I'm fairly sure that the generated API's should be
>> Hopefully someone from Google can address your other concerns.
> 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 protobuf+unsubscr...@googlegroups.com.
> To post to this group, send email to firstname.lastname@example.org.
> Visit this group at http://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
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to email@example.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.