Github user harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/6829#issuecomment-113659788
Yes, all of the libs in the flume-ng/lib directory gets added to the
classpath, so scala would get added to the classpath, but get loaded only as
required (which is normal JVM protocol). We'd have to bump our dependency to
1.6.0 for scala to be automagically available.
Even if we don't upgrade, we don't need to change the dependency set, as
the behavior is the same as before (add scala to flume-ng/lib or plugins dir).
Apart from the assembly part, nothing else changes. I am sending a PR soon to
get rid of the commons-lang3 dependency anyway
---
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
