[
https://issues.apache.org/jira/browse/HBASE-19735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320514#comment-16320514
]
Josh Elser commented on HBASE-19735:
------------------------------------
bq. 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.
Neat! There's definitely a bit of untangling to do down in the Hadoop layer
too. Tons of Jetty and Jackson stuff coming up which we don't actually need. My
first goal is to get _something_ functional/OK, and then return to continue in
the footsteps of others to prune more unneeded dependencies.
bq. Say more on why the new module sir.
Either I haven't found the right documentation to explain what's going on, or I
just fundamentally misunderstand how the assembly plugin's descriptors work :)
I keep having a problem where the pom's dependencies are included in lib/
regardless of what the {{<include>}}'s say. The quickest way I could figure out
to work around that was to create a new module that doesn't have this problem.
Having a similar problem now trying to omit the transitive dependencies of the
shaded client/mapreduce jars as well. Hopefully will have some progress to show
today.
bq. New module depends on hbase-server and replication. Should it?
We need hbase-server as hbase-mapreduce depends on it (maybe not directly is
your point). Replication is probably an oversight.
> 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)
