IIRC, we also shaded Guava in CDH3 into something like org.apache.hadoop.thirdparty.com.google.guava.
-Todd On Mon, Jul 2, 2012 at 9:28 AM, Lars H <[email protected]> wrote: > That is the best argument I heard so far. I'll commit the patch today. > > Thanks. > > -- Lars > > Roman Shaposhnik <[email protected]> schrieb: > > >On Sat, Jun 30, 2012 at 5:24 PM, lars hofhansl <[email protected]> > wrote: > >> So will Guava 11.0.2 in hbase 0.94 be a problem? Should we not update > Guava (at least not until 0.96)? > > > >In general, I don't think there's good answer to how dependencies > >are supposed to be managed wrt. version numbers. After all, all > >of the Hadoop ecosystem projects have to deal with the fact that > >there's at least half a dozen different branches of Hadoop they have > >to work with. It is virtually guaranteed that whatever you do you will > >end up incompatible with one of those builds and most likely the > >version of a dependency that wins will be the one that Hadoop is using. > > > >IOW, whatever is specified in the POM file of individual projects is > >likely to be overridden anyway and the best the could be done > >is to avoid known gaping incompatibility holes (of which I'm not > >aware of too many). > > > >Thanks, > >Roman. > -- Todd Lipcon Software Engineer, Cloudera
