From ce1ebc0124a8b31e8ab8462fa40bc5cc8840246f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ionu=C8=9B=20G=2E=20Stan?= Date: Sat, 9 Sep 2017 13:25:42 +0300 Subject: [PATCH] Use latest version in README.md examples --- README.md | 16 ++++++++-------- doc/README.md | 16 ++++++++-------- 2 files changed, 16 insertions(+), 16 deletions(-) diff --git a/README.md b/README.md index 51489be6a..dc8ef45d6 100644 --- a/README.md +++ b/README.md @@ -111,8 +111,8 @@ $ ./coursier fetch org.apache.spark:spark-sql_2.11:1.6.1 com.twitter:algebird-sp Add to your `build.sbt` ```scala libraryDependencies ++= Seq( - "io.get-coursier" %% "coursier" % "1.0.0-RC10", - "io.get-coursier" %% "coursier-cache" % "1.0.0-RC10" + "io.get-coursier" %% "coursier" % "1.0.0-RC11", + "io.get-coursier" %% "coursier-cache" % "1.0.0-RC11" ) ``` @@ -215,7 +215,7 @@ of the cache used by a particular project, in case you have any doubt about what Enable the SBT plugin globally by adding ```scala -addSbtPlugin("io.get-coursier" % "sbt-coursier" % "1.0.0-RC10") +addSbtPlugin("io.get-coursier" % "sbt-coursier" % "1.0.0-RC11") ``` to `~/.sbt/0.13/plugins/build.sbt` @@ -368,7 +368,7 @@ The `bootstrap` generates tiny bootstrap launchers, able to pull their dependenc repositories on first launch. For example, the launcher of coursier is [generated](https://github.com/coursier/coursier/blob/master/scripts/generate-launcher.sh) with a command like ``` $ ./coursier bootstrap \ - io.get-coursier:coursier-cli_2.11:1.0.0-RC10 \ + io.get-coursier:coursier-cli_2.11:1.0.0-RC11 \ -b -f -o coursier \ -M coursier.cli.Coursier ``` @@ -380,12 +380,12 @@ See `./coursier bootstrap --help` for a list of the available options. Add to your `build.sbt` ```scala libraryDependencies ++= Seq( - "io.get-coursier" %% "coursier" % "1.0.0-RC10", - "io.get-coursier" %% "coursier-cache" % "1.0.0-RC10" + "io.get-coursier" %% "coursier" % "1.0.0-RC11", + "io.get-coursier" %% "coursier-cache" % "1.0.0-RC11" ) ``` -The first module, `"io.get-coursier" %% "coursier" % "1.0.0-RC10"`, mainly depends on +The first module, `"io.get-coursier" %% "coursier" % "1.0.0-RC11"`, mainly depends on `scalaz-core` (and only it, *not* `scalaz-concurrent` for example). It contains among others, definitions, mainly in [`Definitions.scala`](https://github.com/coursier/coursier/blob/master/core/shared/src/main/scala/coursier/core/Definitions.scala), @@ -395,7 +395,7 @@ that expects to be given metadata, wrapped in any `Monad`, then feeds these to ` you the final `Resolution`, wrapped in the same `Monad` it was given input. This final `Resolution` has all the dependencies, including the transitive ones. -The second module, `"io.get-coursier" %% "coursier-cache" % "1.0.0-RC10"`, is precisely in charge of fetching +The second module, `"io.get-coursier" %% "coursier-cache" % "1.0.0-RC11"`, is precisely in charge of fetching these input metadata. It uses `scalaz.concurrent.Task` as a `Monad` to wrap them. It also fetches artifacts (JARs, etc.). It caches all of these (metadata and artifacts) on disk, and validates checksums too. diff --git a/doc/README.md b/doc/README.md index 72cdc5925..e721b698b 100644 --- a/doc/README.md +++ b/doc/README.md @@ -111,8 +111,8 @@ $ ./coursier fetch org.apache.spark:spark-sql_2.11:1.6.1 com.twitter:algebird-sp Add to your `build.sbt` ```scala libraryDependencies ++= Seq( - "io.get-coursier" %% "coursier" % "1.0.0-RC10", - "io.get-coursier" %% "coursier-cache" % "1.0.0-RC10" + "io.get-coursier" %% "coursier" % "1.0.0-RC11", + "io.get-coursier" %% "coursier-cache" % "1.0.0-RC11" ) ``` @@ -242,7 +242,7 @@ of the cache used by a particular project, in case you have any doubt about what Enable the SBT plugin globally by adding ```scala -addSbtPlugin("io.get-coursier" % "sbt-coursier" % "1.0.0-RC10") +addSbtPlugin("io.get-coursier" % "sbt-coursier" % "1.0.0-RC11") ``` to `~/.sbt/0.13/plugins/build.sbt` @@ -397,7 +397,7 @@ The `bootstrap` generates tiny bootstrap launchers, able to pull their dependenc repositories on first launch. For example, the launcher of coursier is [generated](https://github.com/coursier/coursier/blob/master/scripts/generate-launcher.sh) with a command like ``` $ ./coursier bootstrap \ - io.get-coursier:coursier-cli_2.11:1.0.0-RC10 \ + io.get-coursier:coursier-cli_2.11:1.0.0-RC11 \ -b -f -o coursier \ -M coursier.cli.Coursier ``` @@ -409,12 +409,12 @@ See `./coursier bootstrap --help` for a list of the available options. Add to your `build.sbt` ```scala libraryDependencies ++= Seq( - "io.get-coursier" %% "coursier" % "1.0.0-RC10", - "io.get-coursier" %% "coursier-cache" % "1.0.0-RC10" + "io.get-coursier" %% "coursier" % "1.0.0-RC11", + "io.get-coursier" %% "coursier-cache" % "1.0.0-RC11" ) ``` -The first module, `"io.get-coursier" %% "coursier" % "1.0.0-RC10"`, mainly depends on +The first module, `"io.get-coursier" %% "coursier" % "1.0.0-RC11"`, mainly depends on `scalaz-core` (and only it, *not* `scalaz-concurrent` for example). It contains among others, definitions, mainly in [`Definitions.scala`](https://github.com/coursier/coursier/blob/master/core/shared/src/main/scala/coursier/core/Definitions.scala), @@ -424,7 +424,7 @@ that expects to be given metadata, wrapped in any `Monad`, then feeds these to ` you the final `Resolution`, wrapped in the same `Monad` it was given input. This final `Resolution` has all the dependencies, including the transitive ones. -The second module, `"io.get-coursier" %% "coursier-cache" % "1.0.0-RC10"`, is precisely in charge of fetching +The second module, `"io.get-coursier" %% "coursier-cache" % "1.0.0-RC11"`, is precisely in charge of fetching these input metadata. It uses `scalaz.concurrent.Task` as a `Monad` to wrap them. It also fetches artifacts (JARs, etc.). It caches all of these (metadata and artifacts) on disk, and validates checksums too.