On Mon, Jan 27, 2014 at 5:43 AM, Jay Vyas <jayunit...@gmail.com> wrote:
> 1) Can you clarify what is meant by "we drive different dependencies off of
> our BOM the
> artifacts end up being different anyway :-("?
>
> Sorry ... Still learning the bigtop vernacular. :).
Basically I am referring to the fact that within Bigtop all component
dependencies
are just that -- within Bigtop. IOW, Bigtop's HBase build will be
forced to build against
the version of Hadoop that is part of the same BOM, not the default
version of Hadoop
that is defined in upstream HBase pom. Since we drive dependencies in
this way we
are essentially changing the artifacts.
> 2) Now in the interim. My current thought is that pig,hive, etc aren't ever
> gauranteed to
> have non conflicting classpaths. And thus any hadoop app which attempts to
> integrate
> them into a single build will have to use stuff like submodules or profiles.
This one I am quite sure I follow.
Thanks,
Roman.
