diff options
author | Nikolay Tatarinov <5min4eq.unity@gmail.com> | 2017-12-28 09:12:11 +0300 |
---|---|---|
committer | Li Haoyi <haoyi.sg@gmail.com> | 2017-12-27 22:12:11 -0800 |
commit | cb3c5f06b17de55a3d64faab79c081642b0c5a59 (patch) | |
tree | 1307a5469be85c6c4ad39553453d1d7ab3ac7255 | |
parent | 9e27dbb1e8810d2747dc3e45c358abb65fef8b34 (diff) | |
download | mill-cb3c5f06b17de55a3d64faab79c081642b0c5a59.tar.gz mill-cb3c5f06b17de55a3d64faab79c081642b0c5a59.tar.bz2 mill-cb3c5f06b17de55a3d64faab79c081642b0c5a59.zip |
update readme: remove `run` from command line examples (#82)
-rw-r--r-- | readme.md | 16 |
1 files changed, 8 insertions, 8 deletions
@@ -22,16 +22,16 @@ core unit tests e.g.: ```bash -./bin/target/mill run Core.compile -./bin/target/mill run Core.test.compile -./bin/target/mill run Core.test -./bin/target/mill run ScalaPlugin.assembly +./bin/target/mill Core.compile +./bin/target/mill Core.test.compile +./bin/target/mill Core.test +./bin/target/mill ScalaPlugin.assembly ``` There is already a `watch` option that looks for changes on files, e.g.: ```bash -./bin/target/mill --watch run Core.compile +./bin/target/mill --watch Core.compile ``` Output will be generated into a the `./out` folder. @@ -171,7 +171,7 @@ dependency graph of `Task`s. ### Builds are hierarchical -The syntax for running targets from the command line `mill run Foo.bar.baz` is +The syntax for running targets from the command line `mill Foo.bar.baz` is the same as referencing a target in Scala code, `Foo.bar.baz` Everything that you can run from the command line lives in an object hierarchy @@ -181,7 +181,7 @@ able to run it. Cross builds, using the `Cross` data structure, are just another kind of node in the object hierarchy. The only difference is syntax: from the command line you'd -run something via `mill run Core.cross[a].printIt` while from code you use +run something via `mill Core.cross[a].printIt` while from code you use `Core.cross("a").printIt` due to different restrictions in Scala/Bash syntax. ### Caching by default @@ -331,7 +331,7 @@ example, a `Target` at position `Core.test.compile` would: - Output files to the folder `out/Core/test/compile/` -- Be runnable from the command-line via `mill run Core.test.compile` +- Be runnable from the command-line via `mill Core.test.compile` - Be referenced programmatically (from other `Target`s) via `Core.test.compile` |