Github user nchammas commented on a diff in the pull request:
https://github.com/apache/spark/pull/2014#discussion_r17546110
--- Diff: docs/building-spark.md ---
@@ -159,4 +160,13 @@ 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.
+
+The SBT build is derived from the Maven POM files, and so the same Maven
profiles and variables
+can be set to control the SBT build. For example:
+
+ sbt -Pyarn -Phadoop-2.3 compile
--- End diff --
Do we need to add a bit more color here about how to use `sbt`, to match
what used to be in the GitHub README? Or is this sufficient?
---
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
