Comment #18 on issue 210 by aant...@gmail.com: Java code should detect
incompatible runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
Kenton, I'm not sure I would entirely agree with you about Maven. It
actually follows a common and well-accepted convention of
Comment #16 on issue 210 by gus...@veide.se: Java code should detect
incompatible runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
I like the proposal that the version number is detected in runtime. I would
also propose to add the version number to each
Comment #17 on issue 210 by gus...@veide.se: Java code should detect
incompatible runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
I like the proposal that the version number is detected at runtime. I also
propose that version number is added to each
Comment #15 on issue 210 by ken...@google.com: Java code should detect
incompatible runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
Urgh, this is problematic. When people declare a dependency on protocol
buffers, I want them to be able to use the version
Updates:
Cc: liuj...@google.com
Comment #13 on issue 210 by liuj...@google.com: Java code should detect
incompatible runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
Hmm, not very clear about the maven version compatibility... So suppose you
have a
Comment #14 on issue 210 by aantono: Java code should detect incompatible
runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
It would if you specify, what Maven calls, a range - [1.0,2.0), which
would basically read that anything inclusive between 1.0 and 2.0,
Comment #11 on issue 210 by ken...@google.com: Java code should detect
incompatible runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
Right. My point is that the so version isn't expected to relate to
anything else, whereas I suspect that the version on the
Comment #7 on issue 210 by temporal: Java code should detect incompatible
runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
The thing is, the Libtool docs very explicitly say This SO version number
should have nothing at all to do with your project version
Comment #8 on issue 210 by aantono: Java code should detect incompatible
runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
I would dare to say yes, as the protobuf-java jar doen't really have much
to do with the protoc version. Just like in C, the *.so file is
Comment #9 on issue 210 by temporal: Java code should detect incompatible
runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
It is actually very important that you match protoc versions with
libprotobuf.jar versions. However, in the future we'd like to spin off
Comment #10 on issue 210 by aantono: Java code should detect incompatible
runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
So how is it different from using protoc to generate the C code and have
that be bound to a particular version of *.so? Isn't the same
Updates:
Summary: Java code should detect incompatible runtime library version
Status: Accepted
Comment #3 on issue 210 by ken...@google.com: Java code should detect
incompatible runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
Yes, only exact
Comment #4 on issue 210 by aantono: Java code should detect incompatible
runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
Kenton, one of the reasons we've created the shared model artifact that
is pre-compiled is to avoid re-generation of src files and
Comment #5 on issue 210 by ken...@google.com: Java code should detect
incompatible runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
Kenton, one of the reasons we've created the shared model artifact
that is
pre-compiled is to avoid re-generation of src files
Comment #6 on issue 210 by aantono: Java code should detect incompatible
runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
In java, the same can be done when publishing the protobuf-java.jar.
Right now, if you look into the 'java' folder of the project, the
15 matches
Mail list logo
