Sergei Ivanov

@ludoch You may want to take a look at this issue that was opened 2 years ago in the original protobuf project: https://code.google.com/p/protobuf/issues/detail?id=476 The net result so far is that...

...and to give credit where credit is due, I am eternally grateful to David, Brice and other contributors to the initial GitHub version of the plugin. You've done a marvellous...

The original protobuf developers effectively abandoned the plugin many years ago, citing their lack of Maven expertise as a reason (which was fair enough). If this is still the case,...

@ludoch I think an amicable settlement is still entirely possible. I shall let you figure out with the fellow googlers how the plugin is going to be supported going forward....

@ludoch I think it is time to close this thread. We have reached an amicable agreement on licensing with Google, and the plugin has a new home now. https://www.xolstice.org/protobuf-maven-plugin-0.5.0-released/ It...

Adding target/classes is probably unnecessary, I think the only reason you have to do it is because the original plugin incorrectly attaches "namespaced" protos to the resources. Effectively, it flattens...

A general comment is the same as on the pull request #13. I propose that we split out mojos for generating non-java files. This will allow for cleaner separation, flexible...

This is a known issue, which has been fixed on my branch long time ago. We rely quite heavily on protobuf namespaces and importing proto definitions from dependencies (both direct...

I was about to do it for all data sources, but had to stop myself, because I wanted to hear some feedback on the proposed changes (much appreciated!). I'll be...

Sorry, it took a few months to get back to this. I have rebased on the latest master, renamed the argument to `ignore_errors` and added it to all data sources....