[
https://issues.apache.org/jira/browse/HADOOP-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860017#action_12860017
]
Tom White commented on HADOOP-6668:
-----------------------------------
To help evaluate this work, I've patched JDiff to add an {{-incompatible}}
option, which only shows incompatible differences. (In fact it shows some false
positives too. That is, changes that are in fact compatible.) Using this
patched JDiff (patch is at
https://sourceforge.net/tracker/?func=detail&aid=2990626&group_id=37160&atid=419055#),
I have produced a diff between 0.20 and trunk with both the patch for this
issue, and HADOOP-6709 applied (I backported the annotations from HADOOP-5073,
and the patch for this issue to 0.20):
http://people.apache.org/~tomwhite/HADOOP-6668/docs/jdiff/changes.html
There are no significant differences here, so I believe that this patch is
ready to be committed. (Note that the changes in org.apache.hadoop.io will
disappear once HADOOP-6698 is in.)
I'd appreciate it if someone could review this change. Thanks.
> Apply audience and stability annotations to classes in common
> -------------------------------------------------------------
>
> Key: HADOOP-6668
> URL: https://issues.apache.org/jira/browse/HADOOP-6668
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
> Reporter: Tom White
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6668.patch, HADOOP-6668.patch, HADOOP-6668.patch
>
>
> Mark private implementation classes with the InterfaceAudience.Private or
> InterfaceAudience.LimitedPrivate annotation to exclude them from user Javadoc
> and JDiff.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
