Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/1813#issuecomment-52553944
Hi Patrick,
Regarding having the compile-scoped dependency in sbt only, the only way I
can think of doing it is to create a profile that is always enabled from the
sbt build, since the dependencies always come from the poms.
I agree that the sbt build is a little hacky with this patch, but at least
it generates the same artifacts as the maven one. So it would avoid "this works
with maven but not with sbt" situations, even though they might be rare.
---
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]
