diff options
author | Li Haoyi <haoyi.sg@gmail.com> | 2018-02-17 14:27:16 -0800 |
---|---|---|
committer | Li Haoyi <haoyi.sg@gmail.com> | 2018-02-17 14:38:46 -0800 |
commit | 8106f467d41ca747ed039e9d8c5909aa7e40dabb (patch) | |
tree | 2e7add294b387d4562b2ca53581ccb2cb25b79bd | |
parent | 75a45f9163034ca9ba126cf07b3f87f3f24b1249 (diff) | |
download | mill-8106f467d41ca747ed039e9d8c5909aa7e40dabb.tar.gz mill-8106f467d41ca747ed039e9d8c5909aa7e40dabb.tar.bz2 mill-8106f467d41ca747ed039e9d8c5909aa7e40dabb.zip |
fixt-readme
-rw-r--r-- | docs/pages/1 - Intro to Mill.md | 6 | ||||
-rw-r--r-- | readme.md | 18 |
2 files changed, 12 insertions, 12 deletions
diff --git a/docs/pages/1 - Intro to Mill.md b/docs/pages/1 - Intro to Mill.md index 8d2c4847..4dd9380e 100644 --- a/docs/pages/1 - Intro to Mill.md +++ b/docs/pages/1 - Intro to Mill.md @@ -1,4 +1,4 @@ -Mill is your shiny new Scala build tool! +[Mill](https://github.com/lihaoyi/mill) is your shiny new Scala build tool! [Confused by SBT](http://www.lihaoyi.com/post/SowhatswrongwithSBT.html)? Frustrated by Maven? Perplexed by Gradle? Give Mill a try! @@ -17,7 +17,7 @@ To get started, download Mill and install it into your system via the following `curl`/`chmod` command: ```bash -sudo curl -L -o /usr/local/bin/mill https://github.com/lihaoyi/mill/releases/download/0.0.7/0.0.7 && sudo chmod +x /usr/local/bin/mill +sudo curl -L -o /usr/local/bin/mill https://github.com/lihaoyi/mill/releases/download/0.1.0/0.1.0 && sudo chmod +x /usr/local/bin/mill ``` The simplest Mill build for a Scala project looks as follows: @@ -308,7 +308,7 @@ JSON it outputs is structured and easily parsed & manipulated. ## IntelliJ Support -Mill supports IntelliJ by default. Use `mill mill.scalalib.GenIdea/idea` to +Mill supports IntelliJ by default. Use `mill mill.scalalib.GenIdeaModule/idea` to generate an IntelliJ project config for your build. This also configures IntelliJ to allow easy navigate & code-completion within @@ -94,14 +94,14 @@ mill bridges[2.12.4].publish --credentials foo --gpgPassphrase bar * Run multiple targets: ```bash -mill --all core.test scalalib.test +mill all core.test scalalib.test ``` **Note**: don't forget to put `--all` flag when you run multiple commands, otherwise the only first command will be run, and subsequent commands will be passed as arguments to the first one. * Run multiple commands with arguments: ```bash -mill --all bridges[2.11.11].publish bridges[2.12.4].publish -- --credentials foo --gpgPassphrase bar +mill all bridges[2.11.11].publish bridges[2.12.4].publish -- --credentials foo --gpgPassphrase bar ``` Here `--credentials foo --gpgPassphrase bar` arguments will be passed to both `bridges[2.11.11].publish` and `bridges[2.12.4].publish` command. @@ -114,21 +114,21 @@ Here brace expansion from bash(or another shell that support brace expansion) co * Run same targets in multiple modules with brace expansion: ```bash -mill --all {core,scalalib,scalajslib,integration}.test +mill all {core,scalalib,scalajslib,integration}.test ``` will run `test` target in `core`, `scalalib`, `scalajslib` and `integration` modules. * Run multiple targets in one module with brace expansion: ```bash -mill --all scalalib.{compile,test} +mill all scalalib.{compile,test} ``` will run `compile` and `test` targets in `scalalib` module. * Run multiple targets in multiple modules: ```bash -mill show --all {core,scalalib}.{scalaVersion,scalaBinaryVersion} +mill all {core,scalalib}.{scalaVersion,scalaBinaryVersion} ``` will run `scalaVersion` and `scalaBinaryVersion` targets in both `core` and `scalalib` modules. @@ -136,7 +136,7 @@ will run `scalaVersion` and `scalaBinaryVersion` targets in both `core` and `sca * Run targets in different cross build modules ```bash -mill --all bridges[{2.11.11,2.12.4}].publish -- --credentials foo --gpgPassphrase bar +mill all bridges[{2.11.11,2.12.4}].publish -- --credentials foo --gpgPassphrase bar ``` will run `publish` command in both `brides[2.11.11]` and `bridges[2.12.4]` modules @@ -146,13 +146,13 @@ tasks: ```bash # Run the `test` command of all top-level modules -mill --all _.test +mill all _.test # Run the `test` command of all modules, top-level or nested -mill --all __.test +mill all __.test # Run `compile` in every cross-module of `bridges` -mill --all bridges[_].compile +mill all bridges[_].compile ``` **Note**: When you run multiple targets with `--all` flag, they are not |