From 1d20be707fde10ce0d4729e4b9d2b79c3175c415 Mon Sep 17 00:00:00 2001 From: Tuncer Ayaz Date: Wed, 14 Jan 2015 20:16:19 +0100 Subject: [PATCH] Document recursive_cmds in -r help string as well {recursive_cmds, []} was already documented as part of the core rebar.config options that gets printed via 'rebar -h', but this wasn't sufficiently informative. To fix this, explain the use of recursive_cmds as part of the -r help string. Reported-by: Stefan Strigler --- src/rebar.erl | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/rebar.erl b/src/rebar.erl index 8f1e940..23c335f 100644 --- a/src/rebar.erl +++ b/src/rebar.erl @@ -488,7 +488,11 @@ option_spec_list() -> {keep_going, $k, "keep-going", undefined, "Keep running after a command fails"}, {recursive, $r, "recursive", boolean, - "Apply commands to subdirs and dependencies"} + "Apply all commands recursively. Alternatively, you can selectively" + " configure what other commands in addition to the always-recursive" + " ones (compile, *-deps) should also be applied recursively." + " For example, to make 'eunit' recursive, add {recursive_cmds, [eunit]}" + " to rebar.config."} ]. %%