spark-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject spark git commit: [SPARK-11056] Improve documentation of SBT build.
Date Mon, 12 Oct 2015 21:24:35 GMT
Repository: spark
Updated Branches:
  refs/heads/branch-1.5 be68a4bcb -> ebbff391a

[SPARK-11056] Improve documentation of SBT build.

This commit improves the documentation around building Spark to
(1) recommend using SBT interactive mode to avoid the overhead of
launching SBT and (2) refer to the wiki page that documents using
SPARK_PREPEND_CLASSES to avoid creating the assembly jar for each

cc srowen

Author: Kay Ousterhout <>

Closes #9068 from kayousterhout/SPARK-11056.

(cherry picked from commit 091c2c3ecd69803d78c2b15a1487046701059d38)
Signed-off-by: Kay Ousterhout <>


Branch: refs/heads/branch-1.5
Commit: ebbff391ac85cab0c0d65df1371340faeebe6f76
Parents: be68a4b
Author: Kay Ousterhout <>
Authored: Mon Oct 12 14:23:29 2015 -0700
Committer: Kay Ousterhout <>
Committed: Mon Oct 12 14:23:56 2015 -0700

 docs/ | 5 +++++
 1 file changed, 5 insertions(+)
diff --git a/docs/ b/docs/
index 4db32cf..de9729f 100644
--- a/docs/
+++ b/docs/
@@ -205,6 +205,11 @@ can be set to control the SBT build. For example:
     build/sbt -Pyarn -Phadoop-2.3 assembly
+To avoid the overhead of launching sbt each time you need to re-compile, you can launch sbt
+in interactive mode by running `build/sbt`, and then run all build commands at the command
+prompt. For more recommendations on reducing build time, refer to the
+[wiki page](
 # Testing with SBT
 Some of the tests require Spark to be packaged first, so always run `build/sbt assembly`
the first time.  The following is an example of a correct (build, test) sequence:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message