Github user rcsenkbeil commented on the pull request:
https://github.com/apache/spark/pull/1929#issuecomment-52309557
@mateiz @som-snytt The summary I have is that this should work for 2.10.x
as it doesn't appear like they are trickling the removal of the class
invalidation from [scala/scala#3884](https://github.com/scala/scala/pull/3884).
I've given more analysis to the internal classpath editing from 2.10 and I
don't see any potential side effects from appending to the existing merged
classpath.
In terms of Spark moving to 2.11(.3 or higher) in the future, one option
would be to simply include a trait mixed in with global that keeps the
functionality they removed. From what I've seen, the only reason they removed
it was because it wasn't used in the compiler or sbt, not that it had any
issues. The underlying functionality wasn't broken, so I don't see any harm in
doing that as a backup.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
