diff --git a/README.md b/README.md index ffd37a5aa..04ffe4576 100644 --- a/README.md +++ b/README.md @@ -73,10 +73,10 @@ Lastly, it can be used programmatically via its [API](#api) and has a Scala JS [ Enable the SBT plugin by adding ```scala -addSbtPlugin("io.get-coursier" % "sbt-coursier" % "1.0.0") +addSbtPlugin("io.get-coursier" % "sbt-coursier" % "1.0.1-M1") ``` to `~/.sbt/0.13/plugins/build.sbt` (enables it globally), or to the `project/plugins.sbt` file -of an SBT project. Tested with SBT 0.13.8 / 0.13.9 / 0.13.11 / 0.13.12 / 0.13.13 / 0.13.15 / 0.13.16-M1 / 1.0.0-M5. +of an SBT project. Tested with SBT 0.13.8 / 0.13.9 / 0.13.11 / 0.13.12 / 0.13.13 / 0.13.15 / 0.13.16-M1 / 1.0.1-M1-M5. ### Command-line @@ -126,8 +126,8 @@ echo 'autoload -Uz compinit ; compinit' >> ~/.zshrc Add to your `build.sbt` ```scala libraryDependencies ++= Seq( - "io.get-coursier" %% "coursier" % "1.0.0", - "io.get-coursier" %% "coursier-cache" % "1.0.0" + "io.get-coursier" %% "coursier" % "1.0.1-M1", + "io.get-coursier" %% "coursier-cache" % "1.0.1-M1" ) ``` @@ -230,7 +230,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") +addSbtPlugin("io.get-coursier" % "sbt-coursier" % "1.0.1-M1") ``` to `~/.sbt/0.13/plugins/build.sbt` @@ -405,7 +405,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 \ + io.get-coursier:coursier-cli_2.11:1.0.1-M1 \ -b -f -o coursier \ -M coursier.cli.Coursier ``` @@ -417,12 +417,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", - "io.get-coursier" %% "coursier-cache" % "1.0.0" + "io.get-coursier" %% "coursier" % "1.0.1-M1", + "io.get-coursier" %% "coursier-cache" % "1.0.1-M1" ) ``` -The first module, `"io.get-coursier" %% "coursier" % "1.0.0"`, mainly depends on +The first module, `"io.get-coursier" %% "coursier" % "1.0.1-M1"`, 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), @@ -432,7 +432,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"`, is precisely in charge of fetching +The second module, `"io.get-coursier" %% "coursier-cache" % "1.0.1-M1"`, 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. @@ -612,7 +612,7 @@ $ coursier resolve -t io.circe:circe-core_2.11:0.4.1 From SBT, with sbt-coursier enabled, the command `coursierDependencyTree` prints the dependency tree of the various sub-projects, ``` > coursierDependencyTree -io.get-coursier:coursier_2.11:1.0.0-SNAPSHOT +io.get-coursier:coursier_2.11:1.0.1-M1-SNAPSHOT ├─ com.lihaoyi:fastparse_2.11:0.3.7 | ├─ com.lihaoyi:fastparse-utils_2.11:0.3.7 | | ├─ com.lihaoyi:sourcecode_2.11:0.1.1 @@ -677,7 +677,7 @@ same time, I'd recommend an extreme caution at first, like manually inspecting the metadata files and compare with previous ones, to ensure everything's fine. coursier publishes its artifacts with its own plugin enabled since version -`1.0.0-M2` though, without any apparent problem. +`1.0.1-M1-M2` though, without any apparent problem. #### No wait on locked file @@ -775,15 +775,15 @@ $ cli/target/pack/bin/coursier The first releases were milestones like `0.1.0-M?`. As a launcher, basic Ivy repositories support, and an SBT plugin, were added in the mean time, -coursier is now aiming directly at `1.0.0`. +coursier is now aiming directly at `1.0.1-M1`. The last features I'd like to add until a feature freeze are mainly a better / nicer output, for both the command-line tools and the SBT plugin. -These are tracked via GitHub [issues](https://github.com/coursier/coursier/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0.0), along with other points. +These are tracked via GitHub [issues](https://github.com/coursier/coursier/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0.1-M1), along with other points. Milestones will keep being released until then. Then coursier should undergo `RC` releases, with no new features added, and only fixes and minor refactorings between them. -Once RCs will be considered stable enough, `1.0.0` should be released. +Once RCs will be considered stable enough, `1.0.1-M1` should be released. ## Contributors diff --git a/coursier b/coursier index 0c86791a5..d979e1ae2 100755 Binary files a/coursier and b/coursier differ diff --git a/doc/readme/README.md b/doc/readme/README.md index 07dbf2ca7..c05dd4bbc 100644 --- a/doc/readme/README.md +++ b/doc/readme/README.md @@ -73,10 +73,10 @@ Lastly, it can be used programmatically via its [API](#api) and has a Scala JS [ Enable the SBT plugin by adding ```scala -addSbtPlugin("io.get-coursier" % "sbt-coursier" % "1.0.0") +addSbtPlugin("io.get-coursier" % "sbt-coursier" % "1.0.1-M1") ``` to `~/.sbt/0.13/plugins/build.sbt` (enables it globally), or to the `project/plugins.sbt` file -of an SBT project. Tested with SBT 0.13.8 / 0.13.9 / 0.13.11 / 0.13.12 / 0.13.13 / 0.13.15 / 0.13.16-M1 / 1.0.0-M5. +of an SBT project. Tested with SBT 0.13.8 / 0.13.9 / 0.13.11 / 0.13.12 / 0.13.13 / 0.13.15 / 0.13.16-M1 / 1.0.1-M1-M5. ### Command-line @@ -126,8 +126,8 @@ echo 'autoload -Uz compinit ; compinit' >> ~/.zshrc Add to your `build.sbt` ```scala libraryDependencies ++= Seq( - "io.get-coursier" %% "coursier" % "1.0.0", - "io.get-coursier" %% "coursier-cache" % "1.0.0" + "io.get-coursier" %% "coursier" % "1.0.1-M1", + "io.get-coursier" %% "coursier-cache" % "1.0.1-M1" ) ``` @@ -257,7 +257,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") +addSbtPlugin("io.get-coursier" % "sbt-coursier" % "1.0.1-M1") ``` to `~/.sbt/0.13/plugins/build.sbt` @@ -434,7 +434,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 \ + io.get-coursier:coursier-cli_2.11:1.0.1-M1 \ -b -f -o coursier \ -M coursier.cli.Coursier ``` @@ -446,12 +446,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", - "io.get-coursier" %% "coursier-cache" % "1.0.0" + "io.get-coursier" %% "coursier" % "1.0.1-M1", + "io.get-coursier" %% "coursier-cache" % "1.0.1-M1" ) ``` -The first module, `"io.get-coursier" %% "coursier" % "1.0.0"`, mainly depends on +The first module, `"io.get-coursier" %% "coursier" % "1.0.1-M1"`, 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), @@ -461,7 +461,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"`, is precisely in charge of fetching +The second module, `"io.get-coursier" %% "coursier-cache" % "1.0.1-M1"`, 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. @@ -646,7 +646,7 @@ $ coursier resolve -t io.circe:circe-core_2.11:0.4.1 From SBT, with sbt-coursier enabled, the command `coursierDependencyTree` prints the dependency tree of the various sub-projects, ``` > coursierDependencyTree -io.get-coursier:coursier_2.11:1.0.0-SNAPSHOT +io.get-coursier:coursier_2.11:1.0.1-M1-SNAPSHOT ├─ com.lihaoyi:fastparse_2.11:0.3.7 | ├─ com.lihaoyi:fastparse-utils_2.11:0.3.7 | | ├─ com.lihaoyi:sourcecode_2.11:0.1.1 @@ -711,7 +711,7 @@ same time, I'd recommend an extreme caution at first, like manually inspecting the metadata files and compare with previous ones, to ensure everything's fine. coursier publishes its artifacts with its own plugin enabled since version -`1.0.0-M2` though, without any apparent problem. +`1.0.1-M1-M2` though, without any apparent problem. #### No wait on locked file @@ -809,15 +809,15 @@ $ cli/target/pack/bin/coursier The first releases were milestones like `0.1.0-M?`. As a launcher, basic Ivy repositories support, and an SBT plugin, were added in the mean time, -coursier is now aiming directly at `1.0.0`. +coursier is now aiming directly at `1.0.1-M1`. The last features I'd like to add until a feature freeze are mainly a better / nicer output, for both the command-line tools and the SBT plugin. -These are tracked via GitHub [issues](https://github.com/coursier/coursier/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0.0), along with other points. +These are tracked via GitHub [issues](https://github.com/coursier/coursier/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0.1-M1), along with other points. Milestones will keep being released until then. Then coursier should undergo `RC` releases, with no new features added, and only fixes and minor refactorings between them. -Once RCs will be considered stable enough, `1.0.0` should be released. +Once RCs will be considered stable enough, `1.0.1-M1` should be released. ## Contributors diff --git a/project/Mima.scala b/project/Mima.scala index 025f9028b..c93ec4030 100644 --- a/project/Mima.scala +++ b/project/Mima.scala @@ -26,6 +26,7 @@ object Mima { "1.0.0-RC13", "1.0.0-RC14", "1.0.0", + "1.0.1-M1", "" // binary compatibility versions ) diff --git a/project/project/project/plugins.sbt b/project/project/project/plugins.sbt index 30da87aeb..fa1374ad6 100644 --- a/project/project/project/plugins.sbt +++ b/project/project/project/plugins.sbt @@ -1,7 +1,7 @@ addSbtPlugin("io.get-coursier" % "sbt-coursier" % coursierVersion0) // important: this line is matched / substituted during releases (via sbt-release) -def coursierVersion0 = "1.0.0" +def coursierVersion0 = "1.0.1-M1" // required for just released things resolvers += Resolver.sonatypeRepo("releases") diff --git a/scripts/generate-launcher.sh b/scripts/generate-launcher.sh index 63ceefaa5..8a62af02e 100755 --- a/scripts/generate-launcher.sh +++ b/scripts/generate-launcher.sh @@ -1,6 +1,6 @@ #!/bin/bash -VERSION=1.0.0 +VERSION=1.0.1-M1 CACHE_VERSION=v1 SBTPACK_LAUNCHER="$(dirname "$0")/../cli/target/pack/bin/coursier"