[
https://issues.apache.org/jira/browse/AVRO-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768013#action_12768013
]
Patrick Hunt commented on AVRO-159:
-----------------------------------
Hiram, I took a quick look at this and it differs pretty significantly from the
approach I took:
http://github.com/phunt/avro-maven-plugin
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
code, etc...)
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?
> maven-avro-plugin: Allow maven builds to use avro
> -------------------------------------------------
>
> Key: AVRO-159
> URL: https://issues.apache.org/jira/browse/AVRO-159
> Project: Avro
> Issue Type: New Feature
> Components: java
> Reporter: Hiram Chirino
> Attachments: maven-avro-plugin.tar.gz
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
