[ 
https://issues.apache.org/jira/browse/HBASE-20149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429484#comment-16429484
 ] 

stack commented on HBASE-20149:
-------------------------------

We've always shipped site/doc. We can open new issue to entertain site/doc as 
separate artifact?

.002 changes site.xml so references to devapi are back to the hbase site so you 
get something -- a dev api probably from a different version for now till we do 
publishing doc/api/site per hbase version.

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

Reply via email to