diff options
| author | Tuncer Ayaz <tuncer.ayaz@gmail.com> | 2012-11-05 20:08:48 +0100 |
|---|---|---|
| committer | Jared Morrow <jared@basho.com> | 2014-03-11 21:11:36 +0000 |
| commit | 77a0eb6fe4dca909c6fe63f00b6793ba759f1a63 (patch) | |
| tree | 865da21cd27a7c2c765c02a28aaee42eeaf5aa4f /inttest/tdeps1 | |
| parent | 195d61a4021f5df5604a584f04ed5fbe80cafde7 (diff) | |
Fix #56 (always-on recursion)
Always-on recursive application of all rebar commands causes too many
issues. Recursive application is required for:
1. dealing with dependencies: get-deps, update-deps, and compile of deps
right after get-deps or update-deps
2. projects with a riak-like apps/ project structure and dev process
The vast majority of projects are not structured like riak. Therefore,
moving forward it's best to (by default) restrict recursive behavior to
dealing with deps. This commit does that and also adds command line and
rebar.config options for controlling or configuring recursion. Also, we
introduce two meta commands: prepare-deps (equivalent to rebar -r
get-deps compile) and refresh-deps (equivalent to rebar -r update-deps
compile). riak-like projects can extend the list of recursive commands
(to include 'eunit' and 'compile') by adding
{recursive_cmds, [eunit, compile]} to rebar.config.
Diffstat (limited to 'inttest/tdeps1')
| -rw-r--r-- | inttest/tdeps1/tdeps1_rt.erl | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/inttest/tdeps1/tdeps1_rt.erl b/inttest/tdeps1/tdeps1_rt.erl index 3de1a2b..425402f 100644 --- a/inttest/tdeps1/tdeps1_rt.erl +++ b/inttest/tdeps1/tdeps1_rt.erl @@ -41,7 +41,8 @@ run(_Dir) -> apply_cmds(GitCmds, [{dir, "repo/b"}]), apply_cmds(GitCmds, [{dir, "repo/c"}]), - {ok, _} = retest_sh:run("./rebar get-deps compile", []), + {ok, _} = retest_sh:run("./rebar get-deps", []), + {ok, _} = retest_sh:run("./rebar -r compile", []), true = filelib:is_regular("ebin/a.beam"), ok. |