Hiram, I took a quick look at this and it differs pretty significantly from the approach I took:
In particular I based mine on examples like javacc's plugin, which is more oriented to client use. From
what I see in what you've attached it's more geared to building avro itself (paths in the mojo for avro main code, test
I did my docs in github (textile readme) while you are using maven docs (which is better) and you also
have a more sophisticated pom file.
Can you review my mojo implementation (it's pretty simple) which splits the protocol and compiler (not committed yet,
but you get the idea) into separate goals. I propose that we use my mojo as the basis for the implementation, with
your docs/pom updated to support. What do you think?