[HBASE-20149] Purge dev javadoc from bin tarball (or make a separate tarball of javadoc)

• Type: Sub-task
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Component/s: build, community, documentation
• Hadoop Flags: Reviewed

Release Note

We no longer include dev or dev test javadocs in our binary bundle. We still build them; they are just not included because they were half the size of the resultant tarball.

Here is our story on javadoc as of this commit:

 * apidocs - user facing main api javadocs. currently for a release line, published on website and linked from menu. included in the bin tarball
 * devapidocs - hbase internal javadocs. currently for a release line, published on the website but not linked from the menu. no longer included in the bin tarball.
 * testapidocs - user facing test scope api javadocs. currently for a release line, not published. included in the bin tarball.
 * testdevapidocs - hbase internal test scope javadocs. currently for a release line, not published. no longer included in the bin tarball

• Assignee: Michael Stack
• Reporter: Michael Stack
• Created: 07/Mar/18 16:52
• Updated: 24/Jun/22 18:00
• Resolved: 10/Apr/18 17:18

Description

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.

Issue Links

• is related to: HBASE-20365 start branch-2.0 specific website section
• relates to: HBASE-24630 Purge dev javadoc from client bin tarball
• relates to: HBASE-24629 Review client binary size
• links to: Review Board (branch-2.0)