I'll take a look. Usually marking this as "provided" or something fixes it, but the Mesos world can be a bit different.
On Thu, Oct 22, 2015 at 6:56 AM, Santosh Marella (JIRA) <j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/MYRIAD-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968955#comment-14968955 > ] > > Santosh Marella commented on MYRIAD-80: > --------------------------------------- > > I hate to see multiple jar versions in the classpath. This is definitely > something that we should fix, although we (at MapR) haven't seen runtime > issues so far with hadoop-2.7.0 and Myriad. > > [~jklucar], do you have some cycles to fix this for 0.1.0? > > > Resolve dependency version conflicts > > ------------------------------------ > > > > Key: MYRIAD-80 > > URL: https://issues.apache.org/jira/browse/MYRIAD-80 > > Project: Myriad > > Issue Type: Bug > > Reporter: Jim Klucar > > Fix For: Myriad 0.1.0 > > > > > > The Yarn lib directory contains jars that have different versions than > what appears in the myriad build/libs directory. This causes multiple > versions of libraries to be in the yarn/libs directory if you blindly copy > jars from the build directory. > > Specifcally: > > guava-11.0 vs guava-16.0 > > netty-3.6.2 vs netty-3.7.0 > > This can lead to runtime issues depending on what the classloader finds > vs what the code was tested against. I'm not sure how gradle handles this, > but with maven you can mark things as provided so they don't get included. > However, it may be that the executor jar needs all the jars included. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
