New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compile protobuf files with duplicate imports. #69
Conversation
For example, a.proto imports 'b.proto' and 'c.proto' and b.proto imports 'c.proto' as well, which is a valid case. But when try to compile a.proto, the compiler will complain about something like '{32,erl_lint,{redefine_record,c}}' and '{26,erl_lint,{duplicated_export,{decode_c,1}}}' followed by compilation failure.
Any thoughts on this? |
i think the project is stagnant, no replies for some time now On Friday, August 15, 2014, UglyTroLL notifications@github.com wrote:
|
We have intentionally left this repository at a stable spot. It does not implement all features, nor does it do all the implemented features correctly in all circumstances. I (not speaking for Basho here) have intentions to do a rewrite, and a prototype is already underway, but it is not super-high on the priority list. |
@UglyTroLL - I am reviewing PRs and issues in this repository. I can't accept this PR without a test case. Please provide one if you'd like to see this PR merged. Thanks! 😄 |
@lukebakken The unit test was added |
FYI, this project ( |
Upgrade java protobuf version from 2.4.1 to 2.5.0
For example, a.proto imports 'b.proto' and 'c.proto' and b.proto imports 'c.proto' as well, which is a valid case. But when try to compile a.proto, the compiler will complain about something like '{32,erl_lint,{redefine_record,c}}' and '{26,erl_lint,{duplicated_export,{decode_c,1}}}' followed by compilation failure.
e.g.
could not be compiled with error message: