[
https://issues.apache.org/jira/browse/AVRO-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009528#comment-13009528
]
E. Sammer commented on AVRO-784:
--------------------------------
{quote}We'll need to create a different velocity profile instead of breaking
the current one (perhaps 'bean' instead of 'classic'?) and figure out how to
wire this up to switch types at user request in the
Tool/AntTask/MavenPlugin.{quote}
I made sure the changes didn't break backward compatibility; the only changes
are additions. That said, I guess having a separate template so we can make
instance vars private makes sense.
{quote}I'd like to see some name collision tests too...{quote}
Is there a reasonable (predictable) mangling scheme that really makes sense
though? There's also some nastiness in actually being able to detect collisions
programmatically when we're talking about generated classes without making
significant assumptions about super classes. I suppose an alternative is to
make it all annotation based and allow the user to override the names (or force
them to if they want to avoid collisions).
> SpecificCompiler should generate accessors
> ------------------------------------------
>
> Key: AVRO-784
> URL: https://issues.apache.org/jira/browse/AVRO-784
> Project: Avro
> Issue Type: Improvement
> Components: java
> Affects Versions: 1.5.0
> Reporter: E. Sammer
> Labels: features
> Attachments: avro-784.diff, avro-784.diff
>
>
> Avro's Java SpecificCompiler should generate java bean style accessors.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
