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

Mike Drob commented on HBASE-19735:
-----------------------------------

{quote}
1. hbase-procedure depended on hbase-common test-jar, but only needed it at 
test-time, fixed that in branch-2
2. hbase-spark needed some hbase-common test stuff too, but was relying on it 
coming in implicitly; this cause a compilation issue of hbase-spark test code
{quote}
These are general issues, right? Address in a separate JIRA so those changes 
aren't blocked on this since they seem very uncontroversial?

The clusterid issues you've seen might have been related to HBASE-19694 - any 
desire to start this work up again, Josh?

> 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
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: HBASE-19735.000.patch, HBASE-19735.001.branch-2.patch, 
> HBASE-19735.002.branch-2.patch, HBASE-19770.004.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
(v7.6.3#76005)

Reply via email to