mirror of
https://github.com/correl/rebar.git
synced 2024-11-23 19:19:54 +00:00
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:
parent
473d9fe145
commit
1d20be707f
1 changed files with 5 additions and 1 deletions
|
@ -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."}
|
||||||
].
|
].
|
||||||
|
|
||||||
%%
|
%%
|
||||||
|
|
Loading…
Reference in a new issue