Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/2014#discussion_r16968179
--- Diff: docs/building-with-maven.md ---
@@ -159,4 +159,8 @@ then ship it over to the cluster. We are investigating
the exact cause for this.
The assembly jar produced by `mvn package` will, by default, include all
of Spark's dependencies, including Hadoop and some of its ecosystem projects.
On YARN deployments, this causes multiple versions of these to appear on
executor classpaths: the version packaged in the Spark assembly and the version
on each node, included with yarn.application.classpath. The `hadoop-provided`
profile builds the assembly without including Hadoop-ecosystem projects, like
ZooKeeper and Hadoop itself.
+# Building with SBT
+Maven is the official recommendation for packaging Spark, and is the
"build of reference".
+But SBT is supported for day-to-day development since it can provide much
faster iterative
+compilation. More advanced developers may wish to use SBT.
--- End diff --
I'd describe that the sbt build is configured to use the existing maven
profiles and given an example:
```
sbt -Pyarn -Phadoop-2.3 compile
```
... or something
---
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]
