Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2014#issuecomment-53644873
Yeah so our position on the builds is that we officially recommend Maven
for packaging spark but we support sbt for day-to-day development since it can
provide much faster iteration. So I would be inclined to point towards Maven in
the docs - and allow more advanced developers to use SBT. The reason why it's
hard to "officially" support both is that they use different policies for
dependency resolution - this is just a fundamental difference in the way that
Maven and sbt/ivy work - this isn't typically an issue when doing normal
development, but in deployments it can cause a huge dependency headache. And
supporting both in this regard would be extremely difficult.
---
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]
