SBT/ivy pulls in the most recent version of a JAR in, whereas maven pulls in 
the "closest", where closest is lowest distance/depth from the root.


> On 5 Nov 2015, at 18:53, Marcelo Vanzin <van...@cloudera.com> wrote:
> 
> Seems like it's an sbt issue, not a maven one, so "dependency:tree"
> might not help. Still, the command line would be helpful. I use sbt
> and don't see this.
> 
> On Thu, Nov 5, 2015 at 10:44 AM, Marcelo Vanzin <van...@cloudera.com> wrote:
>> Hi Jeff,
>> 
>> On Tue, Nov 3, 2015 at 2:50 AM, Jeff Zhang <zjf...@gmail.com> wrote:
>>> Looks like it's due to guava version conflicts, I see both guava 14.0.1 and
>>> 16.0.1 under lib_managed/bundles. Anyone meet this issue too ?
>> 
>> What command line are you using to build? Can you run "mvn
>> dependency:tree" (with all the other options you're using) to figure
>> out where guava 16 is coming from? Locally I only see version 14,
>> compiling against hadoop 2.5.0.
>> 
>> --
>> Marcelo
> 
> 
> 
> -- 
> Marcelo
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org
> For additional commands, e-mail: dev-h...@spark.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org
For additional commands, e-mail: dev-h...@spark.apache.org

Reply via email to