Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/1813#issuecomment-51414756
After a side-bar -- I still think `compile` scope is correct for Guava, but
that it can be marked `optional` as an extra safe-guard against people linking
to Spark's Guava accidentally. This seems to be the motivation for `provided`
scope, since it achieves this as a secondary effect. But in the exceptional
case where Spark is being used outside an environment where Spark is provided,
this has the undesirable primary effect of making Spark not execute for lack of
Guava, unless the packager also includes Guava for it. Either way can be made
to work and are equivalent for the common case, where Spark is `provided`.
---
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]
