hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jerry He <jerry...@gmail.com>
Subject Re: [DISCUSS] More Shading
Date Sun, 02 Oct 2016 01:32:29 GMT
How is the proposed going to impact the existing shaded-client and
shaded-server modules, making them unnecessary and go away?
It doesn't seem so.  These modules are supposed to shade HBase and upstream
from downstream users.
The proposed shades and protects hbase, but upstream dependencies can still
leak into downstream?



On Sat, Oct 1, 2016 at 2:33 PM, Andrew Purtell <andrew.purtell@gmail.com>

> > Sean has suggested a pre-build step where in another repo we'd make hbase
> > shaded versions of critical libs, 'release' them (votes, etc.) and then
> > have core depend on these. It be a bunch of work but would make the dev's
> > life easier.
> So when we make changes that require updates to and rebuild of the
> supporting libraries, as a developer I would make local changes, install a
> snapshot of that into the local maven cache, then point the HBase build at
> the snapshot, then do the other half of the work, then push up to both?
> I think this could work.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message