> On 6 Nov 2015, at 17:35, Marcelo Vanzin <van...@cloudera.com> wrote: > > On Fri, Nov 6, 2015 at 2:21 AM, Steve Loughran <ste...@hortonworks.com> wrote: >> Maven's closest-first policy has a different flaw, namely that its not >> always obvious why a guava 14.0 that is two hops of transitiveness should >> take priority over a 16.0 version three hops away. Especially when that 0.14 >> version should have come > > But that's not the case here; guava is a direct dependency of spark, > not a transitive one, and the root pom explicitly sets its version to > 14. sbt is just choosing to ignore that and pick whatever latest > version exists from transitive analysis.
I agree, that's wrong > > Maven would behave similarly if Spark did not declare a direct > dependency on guava, but it does. > I think if you have an indirect dependency, it picks one on the shortest path, so if you aren't explicit, you can still lose control of what's going on... --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
