Github user pwendell commented on the pull request:

    https://github.com/apache/spark/pull/3707#issuecomment-67900813
  
    Also one other thing - could you move the "sbt/sbt" scripts to the "build" 
folder, but write a small script that just invokes "build/sbt" with a notice 
saying that it has moved? Second, could you update the relevant docs to reflect 
both the sbt change (the old sbt/sbt path probably has references to it 
peppered throughout Spark) and the new build/mvn tool? I would say right at the 
top of our maven doc that we now bundle a correctly configured maven 
installation (in docs/building-spark.md). Also, looking at that doc reminds me 
that we should add the following in the script:
    
    ```
    export MAVEN_OPTS="-Xmx2g -XX:MaxPermSize=512M 
-XX:ReservedCodeCacheSize=512m"
    ```
    
    If `MAVEN_OPTS` is unset.


---
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]

Reply via email to