You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Stack <st...@duboce.net> on 2018/03/06 19:29:19 UTC
[DISCUSS] What should we bundle in our bin tarball?
On the vote thread for hbase-2.0.0-beta-2, it was noted that the bulk of
our convenience bin tarball size is test javadoc [1] (~ > 50%). Should our
bin tarball include all possible doc both api and dev api for both test and
user?
I could make it so we do not build dev doc by default or that we do not
include it in our bin tarball? What do you all think?
Thanks,
St.Ack
1.
$ cd hbase-2.0.0-beta-2
$ du -sh *
256K CHANGES.txt
4.0K LEGAL
128K LICENSE.txt
420K NOTICE.txt
4.0K README.txt
184K bin
40K conf
818M docs
620K hbase-webapps
129M lib
$ cd docs/
$ du -sh *
0B _chapters
28K acid-semantics.html
11M apache_hbase_reference_guide.pdf
152M apidocs
32K asciidoctor.css
4.0K book
1.9M book.html
16K bulk-loads.html
20K coc.html
4.0K coderay-asciidoctor.css
116K css
36K cygwin.html
20K dependencies.html
272K dependency-convergence.html
16K dependency-info.html
48K dependency-management.html
332M devapidocs
4.0K doap_Hbase.rdf
16K export_control.html
200K fonts
32K hbase.css
2.5M images
28K img
20K index.html
16K integration.html
16K issue-tracking.html
148K js
28K license.html
16K mail-lists.html
20K metrics.html
24K old_news.html
20K plugin-management.html
20K plugins.html
40K poweredbyhbase.html
16K project-info.html
16K project-reports.html
16K project-summary.html
16K pseudo-distributed.html
16K replication.html
372K repo
16K resources.html
16K source-repository.html
16K sponsors.html
24K supportingprojects.html
32K team-list.html
112M testapidocs
205M testdevapidocs
Re: [DISCUSS] What should we bundle in our bin tarball?
Posted by Josh Elser <el...@apache.org>.
+1
I would also be supportive of ripping it all out for the reasons that
Andrew already stated.
On 3/6/18 3:22 PM, Stack wrote:
> Thanks lads. Let me look at purge of non-user javadocs and at building a
> javadoc-only artifiact (then could purge all javadoc as per Andy).
>
> S
>
> On Tue, Mar 6, 2018 at 11:45 AM, Sean Busbey <bu...@apache.org> wrote:
>
>> if we keep any javadocs in the tarball they should just be the user
>> facing javadocs (wether that includes testapidocs I could go either
>> way). I'd be in favor of dumping the javadocs entirely from the binary
>> tarball.
>>
>> do we know why the apidocs are bigger than our binaries? are we
>> mistakingly include a source rendition in html again?
>>
>> We've been a bit spotty on keeping per-release-line javadocs up to
>> date on the website. To give ourselves an out on that, what about
>> including a release aritfact that's just a tarball of javadocs?
>>
>> On Tue, Mar 6, 2018 at 1:33 PM, Andrew Purtell <ap...@apache.org>
>> wrote:
>>>> I could make it so we do not build dev doc by default or that we do not
>>> include it in our bin tarball?
>>>
>>> The binary tarball is so huge at this point I think getting the size down
>>> by pruning javadoc is reasonable, at least in the short term. We have
>>> javadocs up on our site. They will also be available in Maven and your
>>> favorite IDE should handle the automatic download and use of javadoc
>> jars.
>>>
>>>
>>> On Tue, Mar 6, 2018 at 11:29 AM, Stack <st...@duboce.net> wrote:
>>>
>>>> On the vote thread for hbase-2.0.0-beta-2, it was noted that the bulk of
>>>> our convenience bin tarball size is test javadoc [1] (~ > 50%). Should
>> our
>>>> bin tarball include all possible doc both api and dev api for both test
>> and
>>>> user?
>>>>
>>>> I could make it so we do not build dev doc by default or that we do not
>>>> include it in our bin tarball? What do you all think?
>>>>
>>>> Thanks,
>>>> St.Ack
>>>>
>>>>
>>>> 1.
>>>> $ cd hbase-2.0.0-beta-2
>>>> $ du -sh *
>>>> 256K CHANGES.txt
>>>> 4.0K LEGAL
>>>> 128K LICENSE.txt
>>>> 420K NOTICE.txt
>>>> 4.0K README.txt
>>>> 184K bin
>>>> 40K conf
>>>> 818M docs
>>>> 620K hbase-webapps
>>>> 129M lib
>>>>
>>>> $ cd docs/
>>>> $ du -sh *
>>>> 0B _chapters
>>>> 28K acid-semantics.html
>>>> 11M apache_hbase_reference_guide.pdf
>>>> 152M apidocs
>>>> 32K asciidoctor.css
>>>> 4.0K book
>>>> 1.9M book.html
>>>> 16K bulk-loads.html
>>>> 20K coc.html
>>>> 4.0K coderay-asciidoctor.css
>>>> 116K css
>>>> 36K cygwin.html
>>>> 20K dependencies.html
>>>> 272K dependency-convergence.html
>>>> 16K dependency-info.html
>>>> 48K dependency-management.html
>>>> 332M devapidocs
>>>> 4.0K doap_Hbase.rdf
>>>> 16K export_control.html
>>>> 200K fonts
>>>> 32K hbase.css
>>>> 2.5M images
>>>> 28K img
>>>> 20K index.html
>>>> 16K integration.html
>>>> 16K issue-tracking.html
>>>> 148K js
>>>> 28K license.html
>>>> 16K mail-lists.html
>>>> 20K metrics.html
>>>> 24K old_news.html
>>>> 20K plugin-management.html
>>>> 20K plugins.html
>>>> 40K poweredbyhbase.html
>>>> 16K project-info.html
>>>> 16K project-reports.html
>>>> 16K project-summary.html
>>>> 16K pseudo-distributed.html
>>>> 16K replication.html
>>>> 372K repo
>>>> 16K resources.html
>>>> 16K source-repository.html
>>>> 16K sponsors.html
>>>> 24K supportingprojects.html
>>>> 32K team-list.html
>>>> 112M testapidocs
>>>> 205M testdevapidocs
>>>>
>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Andrew
>>>
>>> Words like orphans lost among the crosstalk, meaning torn from truth's
>>> decrepit hands
>>> - A23, Crosstalk
>>
>
Re: [DISCUSS] What should we bundle in our bin tarball?
Posted by Stack <st...@duboce.net>.
Thanks lads. Let me look at purge of non-user javadocs and at building a
javadoc-only artifiact (then could purge all javadoc as per Andy).
S
On Tue, Mar 6, 2018 at 11:45 AM, Sean Busbey <bu...@apache.org> wrote:
> if we keep any javadocs in the tarball they should just be the user
> facing javadocs (wether that includes testapidocs I could go either
> way). I'd be in favor of dumping the javadocs entirely from the binary
> tarball.
>
> do we know why the apidocs are bigger than our binaries? are we
> mistakingly include a source rendition in html again?
>
> We've been a bit spotty on keeping per-release-line javadocs up to
> date on the website. To give ourselves an out on that, what about
> including a release aritfact that's just a tarball of javadocs?
>
> On Tue, Mar 6, 2018 at 1:33 PM, Andrew Purtell <ap...@apache.org>
> wrote:
> >> I could make it so we do not build dev doc by default or that we do not
> > include it in our bin tarball?
> >
> > The binary tarball is so huge at this point I think getting the size down
> > by pruning javadoc is reasonable, at least in the short term. We have
> > javadocs up on our site. They will also be available in Maven and your
> > favorite IDE should handle the automatic download and use of javadoc
> jars.
> >
> >
> > On Tue, Mar 6, 2018 at 11:29 AM, Stack <st...@duboce.net> wrote:
> >
> >> On the vote thread for hbase-2.0.0-beta-2, it was noted that the bulk of
> >> our convenience bin tarball size is test javadoc [1] (~ > 50%). Should
> our
> >> bin tarball include all possible doc both api and dev api for both test
> and
> >> user?
> >>
> >> I could make it so we do not build dev doc by default or that we do not
> >> include it in our bin tarball? What do you all think?
> >>
> >> Thanks,
> >> St.Ack
> >>
> >>
> >> 1.
> >> $ cd hbase-2.0.0-beta-2
> >> $ du -sh *
> >> 256K CHANGES.txt
> >> 4.0K LEGAL
> >> 128K LICENSE.txt
> >> 420K NOTICE.txt
> >> 4.0K README.txt
> >> 184K bin
> >> 40K conf
> >> 818M docs
> >> 620K hbase-webapps
> >> 129M lib
> >>
> >> $ cd docs/
> >> $ du -sh *
> >> 0B _chapters
> >> 28K acid-semantics.html
> >> 11M apache_hbase_reference_guide.pdf
> >> 152M apidocs
> >> 32K asciidoctor.css
> >> 4.0K book
> >> 1.9M book.html
> >> 16K bulk-loads.html
> >> 20K coc.html
> >> 4.0K coderay-asciidoctor.css
> >> 116K css
> >> 36K cygwin.html
> >> 20K dependencies.html
> >> 272K dependency-convergence.html
> >> 16K dependency-info.html
> >> 48K dependency-management.html
> >> 332M devapidocs
> >> 4.0K doap_Hbase.rdf
> >> 16K export_control.html
> >> 200K fonts
> >> 32K hbase.css
> >> 2.5M images
> >> 28K img
> >> 20K index.html
> >> 16K integration.html
> >> 16K issue-tracking.html
> >> 148K js
> >> 28K license.html
> >> 16K mail-lists.html
> >> 20K metrics.html
> >> 24K old_news.html
> >> 20K plugin-management.html
> >> 20K plugins.html
> >> 40K poweredbyhbase.html
> >> 16K project-info.html
> >> 16K project-reports.html
> >> 16K project-summary.html
> >> 16K pseudo-distributed.html
> >> 16K replication.html
> >> 372K repo
> >> 16K resources.html
> >> 16K source-repository.html
> >> 16K sponsors.html
> >> 24K supportingprojects.html
> >> 32K team-list.html
> >> 112M testapidocs
> >> 205M testdevapidocs
> >>
> >
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> > Words like orphans lost among the crosstalk, meaning torn from truth's
> > decrepit hands
> > - A23, Crosstalk
>
Re: [DISCUSS] What should we bundle in our bin tarball?
Posted by Sean Busbey <bu...@apache.org>.
if we keep any javadocs in the tarball they should just be the user
facing javadocs (wether that includes testapidocs I could go either
way). I'd be in favor of dumping the javadocs entirely from the binary
tarball.
do we know why the apidocs are bigger than our binaries? are we
mistakingly include a source rendition in html again?
We've been a bit spotty on keeping per-release-line javadocs up to
date on the website. To give ourselves an out on that, what about
including a release aritfact that's just a tarball of javadocs?
On Tue, Mar 6, 2018 at 1:33 PM, Andrew Purtell <ap...@apache.org> wrote:
>> I could make it so we do not build dev doc by default or that we do not
> include it in our bin tarball?
>
> The binary tarball is so huge at this point I think getting the size down
> by pruning javadoc is reasonable, at least in the short term. We have
> javadocs up on our site. They will also be available in Maven and your
> favorite IDE should handle the automatic download and use of javadoc jars.
>
>
> On Tue, Mar 6, 2018 at 11:29 AM, Stack <st...@duboce.net> wrote:
>
>> On the vote thread for hbase-2.0.0-beta-2, it was noted that the bulk of
>> our convenience bin tarball size is test javadoc [1] (~ > 50%). Should our
>> bin tarball include all possible doc both api and dev api for both test and
>> user?
>>
>> I could make it so we do not build dev doc by default or that we do not
>> include it in our bin tarball? What do you all think?
>>
>> Thanks,
>> St.Ack
>>
>>
>> 1.
>> $ cd hbase-2.0.0-beta-2
>> $ du -sh *
>> 256K CHANGES.txt
>> 4.0K LEGAL
>> 128K LICENSE.txt
>> 420K NOTICE.txt
>> 4.0K README.txt
>> 184K bin
>> 40K conf
>> 818M docs
>> 620K hbase-webapps
>> 129M lib
>>
>> $ cd docs/
>> $ du -sh *
>> 0B _chapters
>> 28K acid-semantics.html
>> 11M apache_hbase_reference_guide.pdf
>> 152M apidocs
>> 32K asciidoctor.css
>> 4.0K book
>> 1.9M book.html
>> 16K bulk-loads.html
>> 20K coc.html
>> 4.0K coderay-asciidoctor.css
>> 116K css
>> 36K cygwin.html
>> 20K dependencies.html
>> 272K dependency-convergence.html
>> 16K dependency-info.html
>> 48K dependency-management.html
>> 332M devapidocs
>> 4.0K doap_Hbase.rdf
>> 16K export_control.html
>> 200K fonts
>> 32K hbase.css
>> 2.5M images
>> 28K img
>> 20K index.html
>> 16K integration.html
>> 16K issue-tracking.html
>> 148K js
>> 28K license.html
>> 16K mail-lists.html
>> 20K metrics.html
>> 24K old_news.html
>> 20K plugin-management.html
>> 20K plugins.html
>> 40K poweredbyhbase.html
>> 16K project-info.html
>> 16K project-reports.html
>> 16K project-summary.html
>> 16K pseudo-distributed.html
>> 16K replication.html
>> 372K repo
>> 16K resources.html
>> 16K source-repository.html
>> 16K sponsors.html
>> 24K supportingprojects.html
>> 32K team-list.html
>> 112M testapidocs
>> 205M testdevapidocs
>>
>
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
> - A23, Crosstalk
Re: [DISCUSS] What should we bundle in our bin tarball?
Posted by Andrew Purtell <ap...@apache.org>.
> I could make it so we do not build dev doc by default or that we do not
include it in our bin tarball?
The binary tarball is so huge at this point I think getting the size down
by pruning javadoc is reasonable, at least in the short term. We have
javadocs up on our site. They will also be available in Maven and your
favorite IDE should handle the automatic download and use of javadoc jars.
On Tue, Mar 6, 2018 at 11:29 AM, Stack <st...@duboce.net> wrote:
> On the vote thread for hbase-2.0.0-beta-2, it was noted that the bulk of
> our convenience bin tarball size is test javadoc [1] (~ > 50%). Should our
> bin tarball include all possible doc both api and dev api for both test and
> user?
>
> I could make it so we do not build dev doc by default or that we do not
> include it in our bin tarball? What do you all think?
>
> Thanks,
> St.Ack
>
>
> 1.
> $ cd hbase-2.0.0-beta-2
> $ du -sh *
> 256K CHANGES.txt
> 4.0K LEGAL
> 128K LICENSE.txt
> 420K NOTICE.txt
> 4.0K README.txt
> 184K bin
> 40K conf
> 818M docs
> 620K hbase-webapps
> 129M lib
>
> $ cd docs/
> $ du -sh *
> 0B _chapters
> 28K acid-semantics.html
> 11M apache_hbase_reference_guide.pdf
> 152M apidocs
> 32K asciidoctor.css
> 4.0K book
> 1.9M book.html
> 16K bulk-loads.html
> 20K coc.html
> 4.0K coderay-asciidoctor.css
> 116K css
> 36K cygwin.html
> 20K dependencies.html
> 272K dependency-convergence.html
> 16K dependency-info.html
> 48K dependency-management.html
> 332M devapidocs
> 4.0K doap_Hbase.rdf
> 16K export_control.html
> 200K fonts
> 32K hbase.css
> 2.5M images
> 28K img
> 20K index.html
> 16K integration.html
> 16K issue-tracking.html
> 148K js
> 28K license.html
> 16K mail-lists.html
> 20K metrics.html
> 24K old_news.html
> 20K plugin-management.html
> 20K plugins.html
> 40K poweredbyhbase.html
> 16K project-info.html
> 16K project-reports.html
> 16K project-summary.html
> 16K pseudo-distributed.html
> 16K replication.html
> 372K repo
> 16K resources.html
> 16K source-repository.html
> 16K sponsors.html
> 24K supportingprojects.html
> 32K team-list.html
> 112M testapidocs
> 205M testdevapidocs
>
--
Best regards,
Andrew
Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
- A23, Crosstalk