Generally, you can ignore these things. They mean some artifacts packaged other artifacts, and so two copies show up when all the JAR contents are merged.
But here you do show a small dependency convergence problem; beanutils 1.7 is present but beanutills-core 1.8 is too even though these should be harmonized. I imagine one could be excluded; I imagine we could harmonize the version manually. In practice, I also imagine it doesn't cause any problem but feel free to propose a fix along those lines. On Thu, Apr 9, 2015 at 4:54 PM, Ritesh Kumar Singh <riteshoneinamill...@gmail.com> wrote: > Hi, > > During compilation I get a lot of these: > > [WARNING] kryo-2.21.jar, reflectasm-1.07-shaded.jar define > 23 overlappping classes: > > [WARNING] commons-beanutils-1.7.0.jar, commons-beanutils-core-1.8.0.jar > define > 82 overlappping classes: > > [WARNING] commons-beanutils-1.7.0.jar, commons-collections-3.2.1.jar, > commons-beanutils-core-1.8.0.jar define 10 overlappping classes: > > > And a lot of others. How do I fix these? --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
