From d0e1b572e88d311e1aee23d92e0384a81de4bcb6 Mon Sep 17 00:00:00 2001 From: Tobias Roeser Date: Wed, 12 Dec 2018 10:38:17 +0100 Subject: Added note about experimental Evaluator commands See https://github.com/lihaoyi/mill/issues/502 --- docs/pages/7 - Extending Mill.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/pages/7 - Extending Mill.md b/docs/pages/7 - Extending Mill.md index 2e59dfe3..70ac24da 100644 --- a/docs/pages/7 - Extending Mill.md +++ b/docs/pages/7 - Extending Mill.md @@ -158,7 +158,9 @@ builds, simply publish your code as a library to maven central. For more information, see Ammonite's [Ivy Dependencies documentation](http://ammonite.io/#import$ivy). -## Evaluator Commands +## Evaluator Commands (experimental) + +_Evaluator Command are experimental and suspected to change. See [issue #502](https://github.com/lihaoyi/mill/issues/502) for details._ You can define a command that takes in the current `Evaluator` as an argument, which you can use to inspect the entire build, or run arbitrary tasks. For @@ -179,3 +181,4 @@ Many built-in tools are implemented as custom evaluator commands: [all](http://www.lihaoyi.com/mill/#all), [inspect](http://www.lihaoyi.com/mill/#inspect), [resolve](http://www.lihaoyi.com/mill/#resolve), [show](http://www.lihaoyi.com/mill/#show). If you want a way to run Mill commands and programmatically manipulate the tasks and outputs, you do so with your own evaluator command. + -- cgit v1.2.3