summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorLi Haoyi <haoyi.sg@gmail.com>2018-09-21 20:02:41 +0800
committerLi Haoyi <haoyi.sg@gmail.com>2018-09-21 20:02:41 +0800
commite27de4a1ea2f4f9186d0963e1dbdd03fe4bb7c00 (patch)
treea4174a1848990aaf10437d117690b98cc1b06fda /docs
parent55e7f92c7796bbaa22db03c656082fb3de855353 (diff)
downloadmill-e27de4a1ea2f4f9186d0963e1dbdd03fe4bb7c00.tar.gz
mill-e27de4a1ea2f4f9186d0963e1dbdd03fe4bb7c00.tar.bz2
mill-e27de4a1ea2f4f9186d0963e1dbdd03fe4bb7c00.zip
0.2.80.2.8
Diffstat (limited to 'docs')
-rw-r--r--docs/pages/1 - Intro to Mill.md13
1 files changed, 9 insertions, 4 deletions
diff --git a/docs/pages/1 - Intro to Mill.md b/docs/pages/1 - Intro to Mill.md
index 82f78527..7af0436b 100644
--- a/docs/pages/1 - Intro to Mill.md
+++ b/docs/pages/1 - Intro to Mill.md
@@ -36,7 +36,7 @@ pacaur -S mill
### Windows
To get started, download Mill from:
-https://github.com/lihaoyi/mill/releases/download/0.2.7/0.2.7, and save it as
+https://github.com/lihaoyi/mill/releases/download/0.2.8/0.2.8, and save it as
`mill.bat`.
If you're using [Scoop](https://scoop.sh) you can install Mill via
@@ -73,7 +73,7 @@ To get started, download Mill and install it into your system via the following
`curl`/`chmod` command:
```bash
-sudo sh -c '(echo "#!/usr/bin/env sh" && curl -L https://github.com/lihaoyi/mill/releases/download/0.2.7/0.2.7) > /usr/local/bin/mill && chmod +x /usr/local/bin/mill'
+sudo sh -c '(echo "#!/usr/bin/env sh" && curl -L https://github.com/lihaoyi/mill/releases/download/0.2.8/0.2.8) > /usr/local/bin/mill && chmod +x /usr/local/bin/mill'
```
### Development Releases
@@ -156,8 +156,8 @@ $ mill -i foo.repl # start an Ammonite REPL within your project
You can run `mill resolve __` to see a full list of the different tasks that are
available, `mill resolve foo._` to see the tasks within `foo`, `mill inspect
-foo.compile` to see what an individual task depends on, or `mill show
-foo.scalaVersion` to inspect the output of any task.
+foo.compile` to inspect a task's doc-comment documentation or what it depends
+on, or `mill show foo.scalaVersion` to show the output of any task.
The most common **tasks** that Mill can run are cached **targets**, such as
`compile`, and un-cached **commands** such as `foo.run`. Targets do not
@@ -767,6 +767,11 @@ is structured with one folder per `Target`/`Command`, that is run, e.g.:
- `out/main/test/forkTest/`
- `out/scalalib/compile/`
+There are also top-level build-related files in the `out/` folder, prefixed as
+`mill-*`. The most useful is `mill-profile.json`, which logs the tasks run and
+time taken for the last Mill command you executed. This is very useful if you
+want to find out exactly what tasks are being run and Mill is being slow.
+
Each folder currently contains the following files:
- `dest/`: a path for the `Task` to use either as a scratch space, or to place