Github user pjopensource commented on the pull request:
https://github.com/apache/spark/pull/693#issuecomment-42554050
yes, it's specific to spark.
2014-05-08 20:52 GMT+08:00 Sean Owen notificati...@github.com:
I don't think it's intended that you use sbt/sbt
Github user pjopensource commented on the pull request:
https://github.com/apache/spark/pull/693#issuecomment-42527084
https://issues.apache.org/jira/browse/SPARK-1759
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/693#issuecomment-42527399
Can one of the admins verify this patch?
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/693#issuecomment-42643489
Yes, maybe someone can double-check me, but I imagine it is meant to show
using just `sbt`. There is no `sbt/` directory created in this sample to begin
with, and the
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/693#issuecomment-42545954
I don't think it's intended that you use `sbt/sbt` for other projects. It's
specific to Spark. Right? You can use the regular `sbt` app of course.
---
If your project is
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/693#issuecomment-42910766
Do you mind closing this if it is no longer necessary? Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user pjopensource opened a pull request:
https://github.com/apache/spark/pull/693
SPARK-1759
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pjopensource/spark branch-0.9
Alternatively you can review and apply these
