On Sun, Feb 6, 2011 at 12:50 PM, Marco@worldcorp wrote:
>
Do i need to somehow declare extensions whenever i register my
> ProtocolDecoder / ProtocolEncoder?
>
I don't know what ProtocolDecoder/ProtocolEncoder are, but yes, you need to
provide an ExtensionRegistry to the parsing method. See
htt
Yes, this code was added in 2.4.0.
On Fri, Feb 4, 2011 at 7:06 AM, dear chap wrote:
> Unfortunately we have to use the particular compiler in question and
> cannot upgrade. Is the
> DescriptorBuilder::OptionInterpreter::AggregateOptionFinder new code ?
> I dont see this problem with protobuf-2.3
I'm not aware of anything in the Java library that provides this
functionality.
On Fri, Feb 4, 2011 at 6:45 AM, Ben Wright wrote:
> Anyone know if this can be accomplished without resorting to JNI?
>
> On Feb 3, 4:01 pm, Jason Hsueh wrote:
> > C++'s FileDescriptor::DebugString() produces text t
I'm starting to look at the patch (meant to start end of last week but got
caught up in other stuff)
On Tue, Feb 1, 2011 at 9:30 PM, Kenton Varda wrote:
> On Tue, Feb 1, 2011 at 3:17 PM, Jason Hsueh wrote:
>
>> Conceptually this sounds great, the big question to me is whether this
>> should be
With protoc (the standard compiler), this should produce a simple error.
Since Ken said he "got StackOverFlow exception", it sounds like he's using
some other compiler (not written in C++).
On Mon, Feb 7, 2011 at 10:26 AM, Pherl Liu wrote:
> You probably need to break up your proto files to eli
You probably need to break up your proto files to eliminate the circular
dependency.. (i.e. have multiple .proto files for a package, and only import
necessary .proto files).
On Mon, Feb 7, 2011 at 5:42 PM, Ken wrote:
> Hi,
>
> I have two proto files: A.proto and B.proto. If I import package B i
Re-adding the list so that someone can consider these problems.
On Mon, Feb 7, 2011 at 5:10 AM, Jim Olson wrote:
> I think it was gcc/g++ 3.3, yes it's a couple years old.
>
> Other problems I discovered :
> protoc has to be installed parallel to the java/src dir
> otherwise the maven pom.xml ca
Comment #3 on issue 250 by g...@google.com: [PATCH] Maven-plugin does not
work with M2Eclipse
http://code.google.com/p/protobuf/issues/detail?id=250
Does the alternate plugin discussed in Issue 81 work with M2Eclipse?
--
You received this message because you are subscribed to the Google Grou
Updates:
Blockedon: 81
Comment #2 on issue 250 by g...@google.com: [PATCH] Maven-plugin does not
work with M2Eclipse
http://code.google.com/p/protobuf/issues/detail?id=250
(No comment was entered for this change.)
--
You received this message because you are subscribed to the Google
Issue 81: Maven Protoc Plugin Code Review
http://code.google.com/p/protobuf/issues/detail?id=81
This issue is now blocking issue 250.
See http://code.google.com/p/protobuf/issues/detail?id=250
--
You received this message because you are listed in the owner
or CC fields of this issue, or because
Hi,
I have two proto files: A.proto and B.proto. If I import package B in
A and import A in B, I got StackOverFlow exception during compiling.
Does anyone know any sulotion for it?
Thanks,
Ken
--
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" grou
11 matches
Mail list logo
