Status: New
Labels: Type-Defect Priority-Medium

New issue 566 by Support in generated Java code for @NonNullByDefault in package

What steps will reproduce the problem?
1. I have switched to using the Eclipse null checking, where-in I add @NonNullByDefault to my file. 2. If I generate the code and place it into the package with the rest of my code (not doing so is the work-around for this issue) then I get errors in the generated code because of it not initializing variables so that they may be null at time of use.

What is the expected output? What do you see instead?
I'd like to see the generated Java code either be written such that there are no issues will nullness, or failing that to have the option to request protoc to include the correct nullness indications.

What version of the product are you using? On what operating system?
Version & platform are not really an issue for this report, but I am using: libprotoc 2.5.0, JDK build 1.7.0_40-b43, Eclipse Kepler Release
Build id: 20130614-0229.

Please provide any additional information below.
I can provide a sample maven based project that reproduces my reported issue if that's helpful.

You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:

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
Visit this group at
For more options, visit

Reply via email to