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 00:27:58 UTC
[jira] [Updated] (AVRO-988) Java: Add public, private, and
public-deprecated options for SpecificCompiler output
[ https://issues.apache.org/jira/browse/AVRO-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting updated AVRO-988:
------------------------------
Affects Version/s: (was: 1.7.3)
1.7.2
Fix Version/s: 1.7.3
Assignee: Jeff Kolesky
This looks good to me. I'll commit it soon unless someone objects.
> Java: Add public, private, and public-deprecated options for SpecificCompiler output
> -------------------------------------------------------------------------------------
>
> Key: AVRO-988
> URL: https://issues.apache.org/jira/browse/AVRO-988
> Project: Avro
> Issue Type: Improvement
> Components: java
> Affects Versions: 1.7.2
> Reporter: Scott Carey
> Assignee: Jeff Kolesky
> Fix For: 1.7.3
>
> Attachments: AVRO-988.patch
>
>
> The specific compiler produces deprecation warnings in both client code and the specific generated classes themselves. The field visibility should be configurable by the user.
> I propose that the SpecificCompiler for the default template allow for a fieldVisibility option that is one of the below:
> * 'public' fields are public, and not deprecated, this is the 1.5.x behavior
> * 'public-deprecated' fields are public, and marked @Deprecated. This is the default behavior in 1.6.x
> * 'private' fields are private. This may be the default in the future.
--
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