You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2012/11/29 01:11:58 UTC

[jira] [Commented] (AVRO-1209) Include immutable source templates with Maven plugin

    [ https://issues.apache.org/jira/browse/AVRO-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506072#comment-13506072 ] 

Doug Cutting commented on AVRO-1209:
------------------------------------

Thanks for adding the tests so quickly!  I'll plan on committing this tomorrow.

Sure, a combined patch might make things easier.
                
> Include immutable source templates with Maven plugin
> ----------------------------------------------------
>
>                 Key: AVRO-1209
>                 URL: https://issues.apache.org/jira/browse/AVRO-1209
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>    Affects Versions: 1.7.2
>            Reporter: Jeff Kolesky
>            Assignee: Jeff Kolesky
>            Priority: Minor
>         Attachments: AVRO-1209.patch, setter-option-for-compiler.patch, setter-option-for-compiler.patch
>
>
> It would be nice to have mostly immutable classes generated by the Maven plugin for the cases when people want to use Avro specific records as their first class model objects and want some assurances of immutability.  An easy way to accomplish this is with another template set that can be shipped with the compiler artifact.  Since the {{templateDirectory}} of the plugin is already configurable, then to use this one must only change their local configuration.
> This is somewhat related to AVRO-988, but I have removed the field setters in addition to making the fields private.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira