summaryrefslogtreecommitdiff
path: root/readme.md
diff options
context:
space:
mode:
authorLi Haoyi <haoyi.sg@gmail.com>2017-12-30 18:00:18 -0800
committerLi Haoyi <haoyi.sg@gmail.com>2017-12-30 18:14:18 -0800
commit282d9a667b69863fefbddb83ade4b9efbc98b994 (patch)
tree06ef80cf9cfd11b80bde22e1c6cffa61905e139b /readme.md
parent476640d8b78a2d1bc902fcdd15fcef996b73ca2c (diff)
downloadmill-282d9a667b69863fefbddb83ade4b9efbc98b994.tar.gz
mill-282d9a667b69863fefbddb83ade4b9efbc98b994.tar.bz2
mill-282d9a667b69863fefbddb83ade4b9efbc98b994.zip
Make use of `T.command`s `T.ctx().dest` in `ScalaPlugin#test.test` and `forkTest`, and allow users to dump the structured JSON test results via `--show`
Diffstat (limited to 'readme.md')
-rw-r--r--readme.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/readme.md b/readme.md
index 30c473c4..875e9a56 100644
--- a/readme.md
+++ b/readme.md
@@ -34,6 +34,16 @@ There is already a `watch` option that looks for changes on files, e.g.:
./bin/target/mill --watch Core.compile
```
+You can get Mill to show the JSON-structured output for a particular `Target` or
+`Command` using the `--show` flag:
+
+```bash
+./bin/target/mill --show Core.scalaVersion
+./bin/target/mill --show Core.compile
+./bin/target/mill --show Core.assemblyClasspath
+./bin/target/mill --show Core.test
+```
+
Output will be generated into a the `./out` folder.
If you are repeatedly testing Mill manually by running it against the `build.sc`