[protobuf] Re: Issue 344 in protobuf: Compile Error in Visual Studio 2010 and 2011 (developer preview)
Comment #5 on issue 344 by elivei...@gmail.com: Compile Error in Visual Studio 2010 and 2011 (developer preview) http://code.google.com/p/protobuf/issues/detail?id=344 Thanks. I worked around this by disabling the tests. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 298 in protobuf: protobuf jar's manifest should include OSGi metadata
Comment #17 on issue 298 by cjdo...@gmail.com: protobuf jar's manifest should include OSGi metadata http://code.google.com/p/protobuf/issues/detail?id=298 Re: it doesn't seem right to me that we should change protobuf to make it conform to the specification of a certain container. All Apache jars and many, many other popular jars (Spring, Guice, etc) have added OSGi headers, It's a trivial way to be a good citizen in the open source community. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 298 in protobuf: protobuf jar's manifest should include OSGi metadata
Comment #18 on issue 298 by rocketra...@gmail.com: protobuf jar's manifest should include OSGi metadata http://code.google.com/p/protobuf/issues/detail?id=298 it doesn't seem right to me that we should change protobuf to make it conform to the specification of a certain container. -- In addition to the other comments, I might also note that, to be completey accurate, you aren't really *changing* protobuf as such. Rather you are *adding* support for many containers and applications that use OSGi meta-data. And the good part is that this addition is trivial and completely compatible with non-OSGi containers and applications. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 298 in protobuf: protobuf jar's manifest should include OSGi metadata
Comment #19 on issue 298 by cvgav...@gmail.com: protobuf jar's manifest should include OSGi metadata http://code.google.com/p/protobuf/issues/detail?id=298 I would like to use protobuf (in its latest version) in my equinox project too... Today I had to use a old version that was wrapped by spring source :( -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 298 in protobuf: protobuf jar's manifest should include OSGi metadata
Comment #20 on issue 298 by m...@thebishops.org: protobuf jar's manifest should include OSGi metadata http://code.google.com/p/protobuf/issues/detail?id=298 Protobuf is about enabling optimal data transfer between devices and servers. OSGi is about java software on mobile devices as well as other platforms. Seems only natural that the java version of protobuf has these headers in its manifest. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 298 in protobuf: protobuf jar's manifest should include OSGi metadata
Comment #21 on issue 298 by xiaof...@google.com: protobuf jar's manifest should include OSGi metadata http://code.google.com/p/protobuf/issues/detail?id=298 I have no idea of how widely OSGi is used in the open source community. Is it the suggested way to add OSGi meta data to every Java jar? -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 298 in protobuf: protobuf jar's manifest should include OSGi metadata
Comment #22 on issue 298 by matteo.c...@gmail.com: protobuf jar's manifest should include OSGi metadata http://code.google.com/p/protobuf/issues/detail?id=298 This is the best way to add suport in my opinion since the manifest file gets generated and there's no room for mistakes there - http://code.google.com/p/protobuf/issues/detail?id=298#c7 Thanks for looking into it. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 298 in protobuf: protobuf jar's manifest should include OSGi metadata
Comment #23 on issue 298 by cjdo...@gmail.com: protobuf jar's manifest should include OSGi metadata http://code.google.com/p/protobuf/issues/detail?id=298 Re: Is it the suggested way to add OSGi meta data to every Java jar? Yes. Increased modularity is Java's future, and OSGi is the dominant mechanism for modularity today. It's trivial to support it and it's very popular. Adding these few header values can increase protobuf's reach with almost no work. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 298 in protobuf: protobuf jar's manifest should include OSGi metadata
Comment #24 on issue 298 by xiaof...@google.com: protobuf jar's manifest should include OSGi metadata http://code.google.com/p/protobuf/issues/detail?id=298 OK, I'll patch the change suggested in comment #7 to the trunk soon. Thanks for your info. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 298 in protobuf: protobuf jar's manifest should include OSGi metadata
Comment #25 on issue 298 by debroux@gmail.com: protobuf jar's manifest should include OSGi metadata http://code.google.com/p/protobuf/issues/detail?id=298 It could be good to have two different artifacts for the full-blown version and the significantly smaller and leaner lite version... if it is possible to distinguish, at runtime, between the full-blown version and the lite version (using some combination of versioned package exports ?). -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 298 in protobuf: protobuf jar's manifest should include OSGi metadata
Comment #26 on issue 298 by rocketra...@gmail.com: protobuf jar's manifest should include OSGi metadata http://code.google.com/p/protobuf/issues/detail?id=298 If you have a lite and full jar, from an OSGi perspective, it is better *not* to distinguish the package exports i.e. for the packages that overlap, the package export spec should be exactly the same. The only difference will be that the full jar will export extra packages. That way users can decide (based on which packages they need to import) which jar they need to use. This approach also lends towards good code structure -- full jar functionality will be isolated at the package level. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
