Thank you very much Ted - that helped beautifully! I think the build system
becomes a product on its own :)

Regards,
  Cos

On Tue, Jun 17, 2014 at 12:40PM, Ted Yu wrote:
> Have you tried the following command ?
> 
> mvn dependency:tree -Dhadoop-two.version=2.3.0
> 
> The output of the above has 2.3.0 as the dependency.
> 
> Cheers
> 
> 
> On Tue, Jun 17, 2014 at 11:40 AM, Konstantin Boudnik <c...@apache.org> wrote:
> 
> > Guys,
> >
> > I have noticed an interesting problem with HBase 0.98 line. I have ended
> > up with
> > a crappy Hadoop 2.2.0 artifacts in my local M2 cache - don't ask me how
> > that
> > happen ;( - which causes compilation problems in HBase. And that brought
> > this
> > whole issue into the light. Here's the essence of it:
> >
> > while running for hbase-server module
> >   % mvn dependency:tree  -Dhadoop.version=2.3.0
> > I am getting a reference to hadoop 2.2.0
> >
> > [INFO] +- org.apache.hadoop:hadoop-common:jar:2.2.0:compile
> > ..
> > [INFO] +- org.apache.hadoop:hadoop-auth:jar:2.2.0:compile
> > [INFO] +- org.apache.hadoop:hadoop-client:jar:2.2.0:compile
> >
> > This only happens for 0.98. On master the reference goes to 2.4.0
> > The problem here is that -Dhadoop.version is being seemingly ignored, which
> > might lead to binaries with dependencies inconsistent with what it was
> > built
> > against. I am not sure if this had came up before, but certainly would
> > appreciate the community's input, if any.
> >
> > Thanks a lot!
> > --
> > Take care,
> >   Cos
> >
> >

Reply via email to