You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/04/10 17:19:00 UTC

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

     [ https://issues.apache.org/jira/browse/HBASE-20149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-20149.
---------------------------
      Resolution: Fixed
        Assignee: stack  (was: Artem Ervits)
    Hadoop Flags: Reviewed

Resolving.

> 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: stack
>            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)