[
https://issues.apache.org/jira/browse/HBASE-19735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320490#comment-16320490
]
stack commented on HBASE-19735:
-------------------------------
bq. .... this "minimal" tarball is only shaving ~3MB off the total size
presently.
Smile. Anything obviously dragged in that shouldn't be there? [~appy] and I
have been using a tool called studio-101 to do the disentangling of modules.
Gives nice visualizations. Shows you in-module, inter-package entanglements too
but graphs are headache-inducing... so we've been hanging out at the coarser
grained module level... Doesn't help w/ external dependencies though. Need
your mvn dependency foo.
> Create a minimal "client" tarball installation
> ----------------------------------------------
>
> Key: HBASE-19735
> URL: https://issues.apache.org/jira/browse/HBASE-19735
> Project: HBase
> Issue Type: New Feature
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 3.0.0
>
> Attachments: HBASE-19735.001.branch-2.patch
>
>
> We're moving ourselves towards more controlled dependencies. A logical next
> step is to try to do the same for our "binary" artifacts that we create
> during releases.
> There is code (our's and our dependency's) which the HMaster and RegionServer
> require which, obviously, clients do not need.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
