diff options
author | Guillaume Galy <guilgaly@users.noreply.github.com> | 2018-05-16 06:19:47 +0200 |
---|---|---|
committer | Nikolay Tatarinov <5min4eq.unity@gmail.com> | 2018-05-16 07:19:47 +0300 |
commit | 730a40d0324c14adfeb3837604c4a65c8e1941b2 (patch) | |
tree | 66587b74d1ee5abba93cfa563dcab3e953d3104c /readme.md | |
parent | 032ae8b5138863c1523cf34a612ba1b19870713b (diff) | |
download | mill-730a40d0324c14adfeb3837604c4a65c8e1941b2.tar.gz mill-730a40d0324c14adfeb3837604c4a65c8e1941b2.tar.bz2 mill-730a40d0324c14adfeb3837604c4a65c8e1941b2.zip |
[WIP] Fixes #227; add `mill clean` (#315)
* Adding clean as a default task
* [WIP] Improve 'clean' paths resolution
* Improve clean targets resolution mechanism
* fix error on clean all
* update "clean all" to keep all 'out/mill-*' paths
* fix cross module resolution in clean task
* Add documentation for "clean" task
Diffstat (limited to 'readme.md')
-rw-r--r-- | readme.md | 11 |
1 files changed, 11 insertions, 0 deletions
@@ -67,6 +67,17 @@ You can get Mill to show the JSON-structured output for a particular `Target` or Output will be generated into a the `./out` folder. +You can clean the project using `clean`: + +```bash +# Clean entire project. +mill clean +# Clean a single target. +mill clean main +# Clean multiple targets. +mill clean main core +``` + If you are repeatedly testing Mill manually by running it against the `build.sc` file in the repository root, you can skip the assembly process and directly run it via: |