[
https://issues.apache.org/jira/browse/HBASE-19735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320690#comment-16320690
]
stack commented on HBASE-19735:
-------------------------------
bq. I keep having a problem where the pom's dependencies are included in lib/
regardless of what the <include>'s say.
I see. Its a while since I messed w/ assembly descriptors. I do remember it an
unwholesome business; poor feedback and lots of guess-work. Would be sweet if
could keep client assembly inside hbase-assembly.. since its only justification
as a module is generating tgzs. It used to do src and bin but now we ask git
for src tgz. Also, in case it helps, this stuff in hbase-assembly has not been
touched in years. Appy came through recently and did some cleanup but general
approach is old... Might not be best place to get inspiration is base point.
Agree w/ your approach of getting something working first... Then pare.
> 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)
