Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9624#issuecomment-155874229
I don't really know what's the source of the problem. My best guess is some
incompatibility between the version of ivy embedded in sbt and the version of
ivy used by Spark, or differences in how they handle dependencies from the
local maven cache. I remember nuking the offending artifacts from the local
maven cache would fix things (ivy would then download fresh copies into its own
cache), but that wasn't a good long-term solution for someone who also uses
maven.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
