From 675d4f9eb1f234860ebd04d9f6e118c287d98eda Mon Sep 17 00:00:00 2001 From: Li Haoyi Date: Sat, 17 Feb 2018 19:39:07 -0800 Subject: Avoid printing top-level tasks twice in `mill resolve __` --- docs/pages/1 - Intro to Mill.md | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'docs/pages') diff --git a/docs/pages/1 - Intro to Mill.md b/docs/pages/1 - Intro to Mill.md index b879dd05..bf9ed926 100644 --- a/docs/pages/1 - Intro to Mill.md +++ b/docs/pages/1 - Intro to Mill.md @@ -66,6 +66,11 @@ $ mill foo.jar # bundle the classfiles into a jar $ mill foo.assembly # bundle classfiles and all dependencies into a jar ``` +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 describe +foo.compile` to see what an individual task depends on, or `mill show +foo.scalaVersion` to inspect 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 re-evaluate unless one of their inputs changes, where-as commands re-run every -- cgit v1.2.3