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
This commit is contained in:
Tuncer Ayaz 2015-01-14 20:16:19 +01:00
parent 473d9fe145
commit 1d20be707f

View file

@ -488,7 +488,11 @@ option_spec_list() ->
{keep_going, $k, "keep-going", undefined, {keep_going, $k, "keep-going", undefined,
"Keep running after a command fails"}, "Keep running after a command fails"},
{recursive, $r, "recursive", boolean, {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."}
]. ].
%% %%