[
https://issues.apache.org/jira/browse/HBASE-20149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431186#comment-16431186
]
Sean Busbey commented on HBASE-20149:
-------------------------------------
i thought of a clearer way to say this. We make 4 javadoc reports:
* apidocs - user facing main api javadocs. currently for a release line,
published on website and linked from menu. included in the bin tarball as of
now and with this patch
* devapidocs - hbase internal javadocs. currently for a release line, published
on the website but not linked from the menu. included in the bin tarball now,
but not after this patch.
* testapidocs - user facing test scope api javadocs. currently for a release
line, not published. included in the bin tarball now and with this patch.
* testdevapidocs - hbase internal test scope javadocs. currently for a release
line, not published. included in the bin tarball now but not after this patch.
does that make sense for the state of play?
300 MiB isn't that much in the scheme of things. I'll go push an addendum.
> Purge dev javadoc from bin tarball (or make a separate tarball of javadoc)
> --------------------------------------------------------------------------
>
> Key: HBASE-20149
> URL: https://issues.apache.org/jira/browse/HBASE-20149
> Project: HBase
> Issue Type: Sub-task
> Components: build, community, documentation
> Reporter: stack
> Assignee: Artem Ervits
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-20149.branch-2.0.001.patch,
> HBASE-20149.branch-2.0.002.patch, HBASE-20149.branch-2.0.003.patch
>
>
> The bin tarball is too fat (Chia-Ping and Josh noticed it on the beta-2
> vote). A note to the dev list subsequently resulted in suggestion that we
> just purge dev javadoc (or even all javadoc) from bin tarball (Andrew). Sean
> was good w/ it and suggested perhaps we could do a javadoc only tgz. Let me
> look into this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
