[
https://issues.apache.org/jira/browse/HBASE-9517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh updated HBASE-9517:
----------------------------------
Resolution: Fixed
Release Note: This updates the javadoc build so that there are two versions
of the javadoc generated -- one version that contains the full internal apis of
hbase, and another that only includes the @InterfaceAudience.Public API that
users and applications will have stronger guarantees on for compatibility
between major and minor versions. The original api location on the website
will contain the more limited api while a new link off the main page will point
to the full internal api. (was: This updates the javadoc build so that there
are two versions of the javadoc generated -- one version that contains the full
internals of hbase, and another that only includes the
@InterfaceAudience.Public API that users and applications will have stronger
guarantees on for compatibility between major and minor versions. The original
api location on the website will contain the more limited api while a new link
off the main page will point to the full internal api.)
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
> Include only InterfaceAudiencePublic elements in generated Javadoc
> ------------------------------------------------------------------
>
> Key: HBASE-9517
> URL: https://issues.apache.org/jira/browse/HBASE-9517
> Project: HBase
> Issue Type: Sub-task
> Components: documentation
> Affects Versions: 0.95.2
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Fix For: 0.98.0, 0.96.0
>
> Attachments: hbase-9517.patch
>
>
> We should generate two sets of javadoc a la HADOOP-6658 -- one for api users
> that excludes all InterfaceAudiencePrivate apis, and one for hbase core
> developers. Eventually when we tighten up the other modules we might add
> another for coproc developers, and other custom 3rd party pluggable elements.
--
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
