follow-up to sbt 1.x changes

Author: xuwei-k

README.md

@@ -125,7 +125,7 @@ Once you've started an `sbt` session you can run one of the core commands:
 If a command results in an error message like `a module is not authorized to depend on
 itself`, it may be that a global SBT plugin (such as [Ensime](http://ensime.org/)) is
 resulting in a cyclical dependency. Try disabling global SBT plugins (perhaps by
-temporarily commenting them out in `~/.sbt/0.13/plugins/plugins.sbt`).
+temporarily commenting them out in `~/.sbt/1.0/plugins/plugins.sbt`).
 
 #### Sandbox
 

admin/init.sh

@@ -15,5 +15,5 @@ sensitive >/dev/null 2>&1
 gpg --list-keys
 gpg --list-secret-keys
 
-mkdir -p ~/.sbt/0.13/plugins
-cp files/gpg.sbt ~/.sbt/0.13/plugins/
+mkdir -p ~/.sbt/1.0/plugins
+cp files/gpg.sbt ~/.sbt/1.0/plugins/

scripts/common

@@ -82,7 +82,7 @@ function checkAvailability () {
 # Only used on Jenkins
 # Generate a repositories file with all allowed repositories in our build environment.
 # Takes a variable number of additional repositories as argument.
-# See http://www.scala-sbt.org/0.13/docs/Proxy-Repositories.html
+# See https://www.scala-sbt.org/1.x/docs/Proxy-Repositories.html
 function generateRepositoriesConfig() {
   echo > "$sbtRepositoryConfig" '[repositories]'
   if [[ $# -gt 0 ]]; then