Oops, I forgot:- Lots of Google software parses .proto files at runtime, and
most of it is written in C++. Java (or Python) dependencies probably would
not be workable.
On Fri, Oct 16, 2009 at 7:34 PM, Kenton Varda wrote:
> This has come up before. There are several reasons why a Java port of
This has come up before. There are several reasons why a Java port of
protoc probably won't fly:- The C/C++ open source community will not accept
Java in their build process.
- Java is not available to all platforms that currently support protocol
buffers.
- Maintaining two complete implementation
On Sat, Oct 17, 2009 at 12:03 AM, maxaf wrote:
>
> The plugin is perfectly usable. I stumbled upon it today during my
> quest to integrate protobuf with a Maven project. Here's what
> transpired:
>
> http://stackoverflow.com/questions/1578456
>
Hmm, so it still requires that you build (on unix)
Greg, I know you're pretty busy, but maybe you could assign this to someone
to finish up?
On Fri, Oct 16, 2009 at 9:03 AM, maxaf wrote:
>
> The plugin is perfectly usable. I stumbled upon it today during my
> quest to integrate protobuf with a Maven project. Here's what
> transpired:
>
> http://
Thanks so much for fixing the message. And your point about symlinks is also
very well taken. Amazing how hard it is to just canonicalize a path! Keep up
the amazing work. The Java mobile-optimized version is soo much faster to
initialize - thanks!
Artem
On Wed, Oct 7, 2009 at 5:42 PM, Kenton Vard
The plugin is perfectly usable. I stumbled upon it today during my
quest to integrate protobuf with a Maven project. Here's what
transpired:
http://stackoverflow.com/questions/1578456
Forget about the damn unit tests. Just get the plugin out into the
wild and end the suspense. It's good to go as