2011-01-31 16:43:31 +00:00
|
|
|
%% -*- erlang-indent-level: 4;indent-tabs-mode: nil -*-
|
2009-12-31 18:42:53 +00:00
|
|
|
%% ex: ts=4 sw=4 et
|
2009-11-29 23:44:30 +00:00
|
|
|
%% -------------------------------------------------------------------
|
|
|
|
%%
|
|
|
|
%% rebar: Erlang Build Tools
|
|
|
|
%%
|
|
|
|
%% Copyright (c) 2009 Dave Smith (dizzyd@dizzyd.com)
|
|
|
|
%%
|
|
|
|
%% Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
|
|
%% of this software and associated documentation files (the "Software"), to deal
|
|
|
|
%% in the Software without restriction, including without limitation the rights
|
|
|
|
%% to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
|
|
%% copies of the Software, and to permit persons to whom the Software is
|
|
|
|
%% furnished to do so, subject to the following conditions:
|
|
|
|
%%
|
|
|
|
%% The above copyright notice and this permission notice shall be included in
|
|
|
|
%% all copies or substantial portions of the Software.
|
|
|
|
%%
|
|
|
|
%% THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
|
|
%% IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
|
|
%% FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
|
|
%% AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
|
|
%% LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
|
|
%% OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
|
|
|
%% THE SOFTWARE.
|
|
|
|
%% -------------------------------------------------------------------
|
|
|
|
-module(rebar_core).
|
|
|
|
|
2012-11-10 20:59:19 +00:00
|
|
|
-export([process_commands/2, help/2]).
|
2009-11-29 23:44:30 +00:00
|
|
|
|
2009-11-29 23:53:53 +00:00
|
|
|
-include("rebar.hrl").
|
|
|
|
|
2010-01-01 13:22:25 +00:00
|
|
|
%% ===================================================================
|
|
|
|
%% Internal functions
|
|
|
|
%% ===================================================================
|
|
|
|
|
2012-11-10 20:59:19 +00:00
|
|
|
help(ParentConfig, Commands) ->
|
|
|
|
%% get all core modules
|
|
|
|
{ok, AnyDirModules} = application:get_env(rebar, any_dir_modules),
|
|
|
|
{ok, RawCoreModules} = application:get_env(rebar, modules),
|
|
|
|
AppDirModules = proplists:get_value(app_dir, RawCoreModules),
|
|
|
|
RelDirModules = proplists:get_value(rel_dir, RawCoreModules),
|
|
|
|
CoreModules = AnyDirModules ++ AppDirModules ++ RelDirModules,
|
|
|
|
|
|
|
|
%% get plugin modules
|
|
|
|
Predirs = [],
|
|
|
|
Dir = rebar_utils:get_cwd(),
|
2013-03-02 15:25:28 +00:00
|
|
|
PredirsAssoc = remember_cwd_predirs(Dir, Predirs),
|
2012-11-10 20:59:19 +00:00
|
|
|
Config = maybe_load_local_config(Dir, ParentConfig),
|
2013-03-02 15:25:28 +00:00
|
|
|
{ok, PluginModules} = plugin_modules(Config, PredirsAssoc),
|
2012-11-10 20:59:19 +00:00
|
|
|
|
|
|
|
AllModules = CoreModules ++ PluginModules,
|
|
|
|
|
|
|
|
lists:foreach(
|
|
|
|
fun(Cmd) ->
|
|
|
|
?CONSOLE("==> help ~p~n~n", [Cmd]),
|
|
|
|
CmdModules = select_modules(AllModules, Cmd, []),
|
|
|
|
Modules = select_modules(CmdModules, info, []),
|
|
|
|
lists:foreach(fun(M) ->
|
|
|
|
?CONSOLE("=== ~p:~p ===~n", [M, Cmd]),
|
|
|
|
M:info(help, Cmd),
|
|
|
|
?CONSOLE("~n", [])
|
|
|
|
end, Modules)
|
|
|
|
end, Commands).
|
|
|
|
|
2012-04-22 19:53:32 +00:00
|
|
|
process_commands([], ParentConfig) ->
|
2012-07-14 21:44:47 +00:00
|
|
|
AbortTrapped = rebar_config:get_xconf(ParentConfig, abort_trapped, false),
|
2012-04-22 19:53:32 +00:00
|
|
|
case {get_operations(ParentConfig), AbortTrapped} of
|
2012-06-04 17:02:36 +00:00
|
|
|
{0, _} ->
|
|
|
|
%% None of the commands had any effect
|
2012-07-28 17:51:57 +00:00
|
|
|
?FAIL;
|
2012-06-04 17:02:36 +00:00
|
|
|
{_, true} ->
|
|
|
|
%% An abort was previously trapped
|
2012-07-28 17:51:57 +00:00
|
|
|
?FAIL;
|
2010-07-25 05:56:46 +00:00
|
|
|
_ ->
|
|
|
|
ok
|
|
|
|
end;
|
2011-06-21 19:46:41 +00:00
|
|
|
process_commands([Command | Rest], ParentConfig) ->
|
2012-04-22 19:53:32 +00:00
|
|
|
%% Reset skip dirs
|
|
|
|
ParentConfig1 = rebar_config:reset_skip_dirs(ParentConfig),
|
2012-07-14 21:44:47 +00:00
|
|
|
Operations = get_operations(ParentConfig1),
|
2012-04-22 19:53:32 +00:00
|
|
|
|
|
|
|
ParentConfig4 =
|
|
|
|
try
|
2012-11-10 20:07:55 +00:00
|
|
|
%% Convert the code path so that all the entries are
|
|
|
|
%% absolute paths. If not, code:set_path() may choke on
|
|
|
|
%% invalid relative paths when trying to restore the code
|
|
|
|
%% path from inside a subdirectory.
|
2012-04-22 19:53:32 +00:00
|
|
|
true = rebar_utils:expand_code_path(),
|
|
|
|
{ParentConfig2, _DirSet} = process_dir(rebar_utils:get_cwd(),
|
2014-04-19 20:01:09 +00:00
|
|
|
Command, ParentConfig1,
|
2012-04-22 19:53:32 +00:00
|
|
|
sets:new()),
|
|
|
|
case get_operations(ParentConfig2) of
|
|
|
|
Operations ->
|
|
|
|
%% This command didn't do anything
|
|
|
|
?CONSOLE("Command '~p' not understood or not applicable~n",
|
|
|
|
[Command]);
|
|
|
|
_ ->
|
2012-06-04 17:02:36 +00:00
|
|
|
ok
|
2012-04-22 19:53:32 +00:00
|
|
|
end,
|
2012-11-10 20:07:55 +00:00
|
|
|
%% TODO: reconsider after config inheritance removal/re-design
|
|
|
|
ParentConfig3 = rebar_config:clean_config(ParentConfig1,
|
|
|
|
ParentConfig2),
|
2012-04-22 19:53:32 +00:00
|
|
|
%% Wipe out vsn cache to avoid invalid hits when
|
|
|
|
%% dependencies are updated
|
|
|
|
rebar_config:set_xconf(ParentConfig3, vsn_cache, dict:new())
|
|
|
|
catch
|
|
|
|
throw:rebar_abort ->
|
2012-07-14 21:44:47 +00:00
|
|
|
case rebar_config:get_xconf(ParentConfig1, keep_going, false) of
|
2012-04-22 19:53:32 +00:00
|
|
|
false ->
|
2012-07-28 17:51:57 +00:00
|
|
|
?FAIL;
|
2012-04-22 19:53:32 +00:00
|
|
|
true ->
|
|
|
|
?WARN("Continuing on after abort: ~p\n", [Rest]),
|
2012-07-14 21:44:47 +00:00
|
|
|
rebar_config:set_xconf(ParentConfig1,
|
|
|
|
abort_trapped, true)
|
2012-04-22 19:53:32 +00:00
|
|
|
end
|
|
|
|
end,
|
|
|
|
process_commands(Rest, ParentConfig4).
|
2009-11-29 23:44:30 +00:00
|
|
|
|
2014-04-19 20:01:09 +00:00
|
|
|
process_dir(Dir, Command, ParentConfig, DirSet) ->
|
2010-03-16 19:30:22 +00:00
|
|
|
case filelib:is_dir(Dir) of
|
|
|
|
false ->
|
|
|
|
?WARN("Skipping non-existent sub-dir: ~p\n", [Dir]),
|
2012-04-22 19:53:32 +00:00
|
|
|
{ParentConfig, DirSet};
|
2012-11-05 19:08:48 +00:00
|
|
|
true ->
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
WouldCd = would_cd_into_dir(Dir, Command, ParentConfig),
|
2010-03-16 19:30:22 +00:00
|
|
|
ok = file:set_cwd(Dir),
|
2011-09-06 08:51:38 +00:00
|
|
|
Config = maybe_load_local_config(Dir, ParentConfig),
|
2010-03-16 19:30:22 +00:00
|
|
|
|
|
|
|
%% Save the current code path and then update it with
|
2012-11-05 19:08:48 +00:00
|
|
|
%% lib_dirs. Children inherit parents code path, but we also
|
|
|
|
%% want to ensure that we restore everything to pristine
|
2010-03-16 19:30:22 +00:00
|
|
|
%% condition after processing this child
|
|
|
|
CurrentCodePath = update_code_path(Config),
|
|
|
|
|
2012-11-05 19:08:48 +00:00
|
|
|
%% Get the list of processing modules and check each one
|
|
|
|
%% against CWD to see if it's a fit -- if it is, use that
|
|
|
|
%% set of modules to process this dir.
|
2010-03-16 19:30:22 +00:00
|
|
|
{ok, AvailModuleSets} = application:get_env(rebar, modules),
|
2011-12-12 18:08:40 +00:00
|
|
|
ModuleSet = choose_module_set(AvailModuleSets, Dir),
|
2014-04-19 20:01:09 +00:00
|
|
|
skip_or_process_dir(Dir, Command, Config, DirSet, CurrentCodePath,
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
ModuleSet, WouldCd)
|
|
|
|
end.
|
|
|
|
|
|
|
|
would_cd_into_dir(Dir, Command, Config) ->
|
|
|
|
case would_cd_into_dir1(Dir, Command, Config) of
|
|
|
|
true ->
|
|
|
|
would_cd;
|
2012-11-05 19:08:48 +00:00
|
|
|
false ->
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
would_not_cd
|
2011-12-18 12:29:58 +00:00
|
|
|
end.
|
|
|
|
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
would_cd_into_dir1(Dir, Command, Config) ->
|
2012-11-05 19:08:48 +00:00
|
|
|
rebar_utils:processing_base_dir(Config, Dir) orelse
|
|
|
|
rebar_config:is_recursive(Config) orelse
|
2014-04-19 20:01:09 +00:00
|
|
|
is_recursive_command(Command, Config) orelse
|
2014-03-30 17:47:31 +00:00
|
|
|
is_generate_in_rel_dir(Command, Dir).
|
2012-11-05 19:08:48 +00:00
|
|
|
|
2014-03-30 17:47:31 +00:00
|
|
|
%% Check whether the command is part of the built-in (or extended via
|
|
|
|
%% rebar.config) list of default-recursive commands.
|
2014-04-19 20:01:09 +00:00
|
|
|
is_recursive_command(Command, Config) ->
|
2012-11-05 19:08:48 +00:00
|
|
|
{ok, AppCmds} = application:get_env(rebar, recursive_cmds),
|
|
|
|
ConfCmds = rebar_config:get_local(Config, recursive_cmds, []),
|
|
|
|
RecursiveCmds = AppCmds ++ ConfCmds,
|
|
|
|
lists:member(Command, RecursiveCmds).
|
|
|
|
|
2014-03-30 17:47:31 +00:00
|
|
|
%% If the directory we're about to process contains
|
|
|
|
%% reltool.config[.script] and the command to be applied is
|
|
|
|
%% 'generate', then it's safe to process. We do this to retain the
|
|
|
|
%% behavior of specifying {sub_dirs, ["rel"]} and have "rebar generate"
|
|
|
|
%% pick up rel/reltool.config[.script]. Without this workaround you'd
|
|
|
|
%% have to run "rebar -r generate" (which you don't want to do if you
|
|
|
|
%% have deps or other sub_dirs) or "cd rel && rebar generate".
|
|
|
|
is_generate_in_rel_dir(generate, Dir) ->
|
|
|
|
case rebar_rel_utils:is_rel_dir(Dir) of
|
|
|
|
{true, _} ->
|
|
|
|
true;
|
|
|
|
false ->
|
|
|
|
false
|
|
|
|
end;
|
|
|
|
is_generate_in_rel_dir(_, _) ->
|
|
|
|
false.
|
|
|
|
|
2014-04-19 20:01:09 +00:00
|
|
|
skip_or_process_dir(Dir, Command, Config, DirSet, CurrentCodePath,
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
{[], undefined}=ModuleSet, WouldCd) ->
|
|
|
|
process_dir1(Dir, Command, Config, DirSet, CurrentCodePath, ModuleSet,
|
|
|
|
WouldCd);
|
2014-04-19 20:01:09 +00:00
|
|
|
skip_or_process_dir(Dir, Command, Config, DirSet, CurrentCodePath,
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
{_, File}=ModuleSet, WouldCd) ->
|
2014-04-19 20:01:09 +00:00
|
|
|
case lists:suffix(".app.src", File)
|
|
|
|
orelse lists:suffix(".app", File) of
|
2012-01-13 18:00:44 +00:00
|
|
|
true ->
|
|
|
|
%% .app or .app.src file, check if is_skipped_app
|
2014-04-19 20:01:09 +00:00
|
|
|
skip_or_process_dir1(Dir, Command, Config, DirSet, CurrentCodePath,
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
ModuleSet, WouldCd, File);
|
2012-01-13 18:00:44 +00:00
|
|
|
false ->
|
2011-12-18 12:29:58 +00:00
|
|
|
%% not an app dir, no need to consider apps=/skip_apps=
|
2014-04-19 20:01:09 +00:00
|
|
|
process_dir1(Dir, Command, Config, DirSet, CurrentCodePath,
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
ModuleSet, WouldCd)
|
2011-12-12 18:08:40 +00:00
|
|
|
end.
|
2010-03-16 19:30:22 +00:00
|
|
|
|
2014-04-19 20:01:09 +00:00
|
|
|
skip_or_process_dir1(Dir, Command, Config, DirSet, CurrentCodePath, ModuleSet,
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
WouldCd, AppFile) ->
|
2012-04-22 19:53:32 +00:00
|
|
|
case rebar_app_utils:is_skipped_app(Config, AppFile) of
|
2013-09-23 19:19:51 +00:00
|
|
|
{Config1, {true, _SkippedApp}} when Command == 'update-deps' ->
|
|
|
|
%% update-deps does its own app skipping. Unfortunately there's no
|
|
|
|
%% way to signal this to rebar_core, so we have to explicitly do it
|
|
|
|
%% here... Otherwise if you use app=, it'll skip the toplevel
|
|
|
|
%% directory and nothing will be updated.
|
2014-04-19 20:01:09 +00:00
|
|
|
process_dir1(Dir, Command, Config1, DirSet, CurrentCodePath,
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
ModuleSet, WouldCd);
|
2012-04-22 19:53:32 +00:00
|
|
|
{Config1, {true, SkippedApp}} ->
|
2011-12-12 18:08:40 +00:00
|
|
|
?DEBUG("Skipping app: ~p~n", [SkippedApp]),
|
2014-04-19 20:01:09 +00:00
|
|
|
{increment_operations(Config1), DirSet};
|
2012-04-22 19:53:32 +00:00
|
|
|
{Config1, false} ->
|
2014-04-19 20:01:09 +00:00
|
|
|
process_dir1(Dir, Command, Config1, DirSet, CurrentCodePath,
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
ModuleSet, WouldCd)
|
2011-12-12 18:08:40 +00:00
|
|
|
end.
|
2010-05-11 15:35:47 +00:00
|
|
|
|
2014-04-19 20:01:09 +00:00
|
|
|
process_dir1(Dir, Command, Config, DirSet, CurrentCodePath,
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
{DirModules, File}, WouldCd) ->
|
2013-10-16 10:29:54 +00:00
|
|
|
Config0 = rebar_config:set_xconf(Config, current_command, Command),
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
|
2011-12-12 18:08:40 +00:00
|
|
|
%% Get the list of modules for "any dir". This is a catch-all list
|
|
|
|
%% of modules that are processed in addition to modules associated
|
|
|
|
%% with this directory type. These any_dir modules are processed
|
|
|
|
%% FIRST.
|
|
|
|
{ok, AnyDirModules} = application:get_env(rebar, any_dir_modules),
|
2010-03-16 19:30:22 +00:00
|
|
|
|
2011-12-12 18:08:40 +00:00
|
|
|
Modules = AnyDirModules ++ DirModules,
|
2011-09-18 07:27:15 +00:00
|
|
|
|
2011-12-12 18:08:40 +00:00
|
|
|
%% Invoke 'preprocess' on the modules -- this yields a list of other
|
|
|
|
%% directories that should be processed _before_ the current one.
|
2014-04-19 20:01:09 +00:00
|
|
|
{Config1, Predirs} = acc_modules(Modules, preprocess, Config0, File),
|
2011-09-18 07:27:15 +00:00
|
|
|
|
2012-12-08 21:07:10 +00:00
|
|
|
%% Remember associated pre-dirs (used for plugin lookup)
|
|
|
|
PredirsAssoc = remember_cwd_predirs(Dir, Predirs),
|
2012-01-14 16:43:25 +00:00
|
|
|
|
2011-12-12 18:08:40 +00:00
|
|
|
%% Get the list of plug-in modules from rebar.config. These
|
|
|
|
%% modules may participate in preprocess and postprocess.
|
2012-12-08 21:07:10 +00:00
|
|
|
{ok, PluginModules} = plugin_modules(Config1, PredirsAssoc),
|
2014-04-19 20:01:09 +00:00
|
|
|
AllModules = Modules ++ PluginModules,
|
2011-09-18 07:27:15 +00:00
|
|
|
|
2014-04-19 20:01:09 +00:00
|
|
|
{Config2, PluginPredirs} = acc_modules(PluginModules, preprocess, Config1,
|
|
|
|
File),
|
2011-09-18 07:27:15 +00:00
|
|
|
|
2011-12-12 18:08:40 +00:00
|
|
|
AllPredirs = Predirs ++ PluginPredirs,
|
2010-06-09 19:16:58 +00:00
|
|
|
|
2011-12-12 18:08:40 +00:00
|
|
|
?DEBUG("Predirs: ~p\n", [AllPredirs]),
|
2014-04-19 20:01:09 +00:00
|
|
|
{Config3, DirSet2} = process_each(AllPredirs, Command, Config2, DirSet,
|
|
|
|
File),
|
2010-06-09 19:16:58 +00:00
|
|
|
|
2011-12-12 18:08:40 +00:00
|
|
|
%% Make sure the CWD is reset properly; processing the dirs may have
|
|
|
|
%% caused it to change
|
|
|
|
ok = file:set_cwd(Dir),
|
2010-06-21 16:24:01 +00:00
|
|
|
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
%% Maybe apply command to Dir
|
|
|
|
Config4 = maybe_execute(Dir, Command, Config3, Modules, PluginModules,
|
|
|
|
AllModules, File, WouldCd),
|
2010-06-09 19:16:58 +00:00
|
|
|
|
2011-12-12 18:08:40 +00:00
|
|
|
%% Mark the current directory as processed
|
|
|
|
DirSet3 = sets:add_element(Dir, DirSet2),
|
2010-06-09 19:16:58 +00:00
|
|
|
|
2011-12-12 18:08:40 +00:00
|
|
|
%% Invoke 'postprocess' on the modules. This yields a list of other
|
|
|
|
%% directories that should be processed _after_ the current one.
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
{Config5, Postdirs} = acc_modules(AllModules, postprocess, Config4, File),
|
2011-12-12 18:08:40 +00:00
|
|
|
?DEBUG("Postdirs: ~p\n", [Postdirs]),
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
Res = process_each(Postdirs, Command, Config5, DirSet3, File),
|
2010-06-09 19:16:58 +00:00
|
|
|
|
2011-12-12 18:08:40 +00:00
|
|
|
%% Make sure the CWD is reset properly; processing the dirs may have
|
|
|
|
%% caused it to change
|
|
|
|
ok = file:set_cwd(Dir),
|
2010-05-11 20:07:13 +00:00
|
|
|
|
2011-12-12 18:08:40 +00:00
|
|
|
%% Once we're all done processing, reset the code path to whatever
|
|
|
|
%% the parent initialized it to
|
|
|
|
restore_code_path(CurrentCodePath),
|
2010-06-09 19:16:58 +00:00
|
|
|
|
2012-06-08 17:34:44 +00:00
|
|
|
%% Return the updated {config, dirset} as result
|
2012-04-22 19:53:32 +00:00
|
|
|
Res.
|
2010-03-16 19:30:22 +00:00
|
|
|
|
Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.
To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.
Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).
So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.
If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true
If you want to test ct suites in all dirs, you have to run
$ rebar -r ct
The fix is not specific to ct and applies to all commands.
To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-20 09:59:41 +00:00
|
|
|
maybe_execute(Dir, Command, Config, Modules, PluginModules, AllModules, File,
|
|
|
|
would_cd) ->
|
|
|
|
%% Check that this directory is not on the skip list
|
|
|
|
case rebar_config:is_skip_dir(Config, Dir) of
|
|
|
|
true ->
|
|
|
|
%% Do not execute the command on the directory, as some
|
|
|
|
%% module has requested a skip on it.
|
|
|
|
?INFO("Skipping ~s in ~s\n", [Command, Dir]),
|
|
|
|
Config;
|
|
|
|
|
|
|
|
false ->
|
|
|
|
%% Check for and get command specific environments
|
|
|
|
{Config1, Env} = setup_envs(Config, Modules),
|
|
|
|
|
|
|
|
%% Execute any before_command plugins on this directory
|
|
|
|
Config2 = execute_pre(Command, PluginModules, Config1, File, Env),
|
|
|
|
|
|
|
|
%% Execute the current command on this directory
|
|
|
|
Config3 = execute(Command, AllModules, Config2, File, Env),
|
|
|
|
|
|
|
|
%% Execute any after_command plugins on this directory
|
|
|
|
execute_post(Command, PluginModules, Config3, File, Env)
|
|
|
|
end;
|
|
|
|
maybe_execute(_Dir, _Command, Config, _Modules, _PluginModules, _AllModules,
|
|
|
|
_File, would_not_cd) ->
|
|
|
|
Config.
|
|
|
|
|
2012-12-08 21:07:10 +00:00
|
|
|
remember_cwd_predirs(Cwd, Predirs) ->
|
2012-01-14 16:43:25 +00:00
|
|
|
Store = fun(Dir, Dict) ->
|
|
|
|
case dict:find(Dir, Dict) of
|
|
|
|
error ->
|
2012-06-08 19:56:18 +00:00
|
|
|
?DEBUG("Associate sub_dir ~s with ~s~n",
|
|
|
|
[Dir, Cwd]),
|
2012-01-14 16:43:25 +00:00
|
|
|
dict:store(Dir, Cwd, Dict);
|
|
|
|
{ok, Existing} ->
|
2012-03-31 17:20:05 +00:00
|
|
|
?ABORT("Internal consistency assertion failed.~n"
|
|
|
|
"sub_dir ~s already associated with ~s.~n"
|
|
|
|
"Duplicate sub_dirs or deps entries?",
|
2012-12-08 21:09:00 +00:00
|
|
|
[Dir, Existing])
|
2012-01-14 16:43:25 +00:00
|
|
|
end
|
|
|
|
end,
|
2012-12-08 21:07:10 +00:00
|
|
|
lists:foldl(Store, dict:new(), Predirs).
|
2012-01-14 16:43:25 +00:00
|
|
|
|
2011-09-06 08:51:38 +00:00
|
|
|
maybe_load_local_config(Dir, ParentConfig) ->
|
|
|
|
%% We need to ensure we don't overwrite custom
|
|
|
|
%% config when we are dealing with base_dir.
|
2012-08-05 17:56:27 +00:00
|
|
|
case rebar_utils:processing_base_dir(ParentConfig, Dir) of
|
2011-09-06 08:51:38 +00:00
|
|
|
true ->
|
|
|
|
ParentConfig;
|
|
|
|
false ->
|
|
|
|
rebar_config:new(ParentConfig)
|
|
|
|
end.
|
2010-05-08 14:07:28 +00:00
|
|
|
|
2010-05-15 20:57:07 +00:00
|
|
|
%%
|
2010-06-09 19:16:58 +00:00
|
|
|
%% Given a list of directories and a set of previously processed directories,
|
|
|
|
%% process each one we haven't seen yet
|
2010-05-15 20:57:07 +00:00
|
|
|
%%
|
2014-04-19 20:01:09 +00:00
|
|
|
process_each([], _Command, Config, DirSet, _File) ->
|
2012-08-04 12:04:27 +00:00
|
|
|
%% reset cached (setup_env) envs
|
|
|
|
Config1 = rebar_config:reset_envs(Config),
|
2012-06-08 17:34:44 +00:00
|
|
|
{Config1, DirSet};
|
2014-04-19 20:01:09 +00:00
|
|
|
process_each([Dir | Rest], Command, Config, DirSet, File) ->
|
2010-06-09 19:16:58 +00:00
|
|
|
case sets:is_element(Dir, DirSet) of
|
2010-05-15 20:57:07 +00:00
|
|
|
true ->
|
2010-06-09 19:16:58 +00:00
|
|
|
?DEBUG("Skipping ~s; already processed!\n", [Dir]),
|
2014-04-19 20:01:09 +00:00
|
|
|
process_each(Rest, Command, Config, DirSet, File);
|
2010-05-15 20:57:07 +00:00
|
|
|
false ->
|
2014-04-19 20:01:09 +00:00
|
|
|
{Config1, DirSet2} = process_dir(Dir, Command, Config, DirSet),
|
2012-04-22 19:53:32 +00:00
|
|
|
Config2 = rebar_config:clean_config(Config, Config1),
|
2012-08-04 12:04:27 +00:00
|
|
|
%% reset cached (setup_env) envs
|
|
|
|
Config3 = rebar_config:reset_envs(Config2),
|
2014-04-19 20:01:09 +00:00
|
|
|
process_each(Rest, Command, Config3, DirSet2, File)
|
2010-03-16 19:30:22 +00:00
|
|
|
end.
|
2009-11-29 23:44:30 +00:00
|
|
|
|
|
|
|
%%
|
2009-12-26 06:19:09 +00:00
|
|
|
%% Given a list of module sets from rebar.app and a directory, find
|
2009-12-12 14:34:29 +00:00
|
|
|
%% the appropriate subset of modules for this directory
|
2009-11-29 23:44:30 +00:00
|
|
|
%%
|
2009-12-12 14:34:29 +00:00
|
|
|
choose_module_set([], _Dir) ->
|
2009-12-26 06:19:09 +00:00
|
|
|
{[], undefined};
|
2010-06-09 19:16:58 +00:00
|
|
|
choose_module_set([{Type, Modules} | Rest], Dir) ->
|
|
|
|
case is_dir_type(Type, Dir) of
|
2009-12-12 14:34:29 +00:00
|
|
|
{true, File} ->
|
2009-12-26 06:19:09 +00:00
|
|
|
{Modules, File};
|
2009-11-29 23:44:30 +00:00
|
|
|
false ->
|
2009-12-12 14:34:29 +00:00
|
|
|
choose_module_set(Rest, Dir)
|
2009-11-29 23:44:30 +00:00
|
|
|
end.
|
|
|
|
|
2010-06-09 19:16:58 +00:00
|
|
|
is_dir_type(app_dir, Dir) ->
|
|
|
|
rebar_app_utils:is_app_dir(Dir);
|
|
|
|
is_dir_type(rel_dir, Dir) ->
|
|
|
|
rebar_rel_utils:is_rel_dir(Dir);
|
|
|
|
is_dir_type(_, _) ->
|
|
|
|
false.
|
2010-05-11 20:07:13 +00:00
|
|
|
|
2012-02-07 19:15:58 +00:00
|
|
|
execute_pre(Command, Modules, Config, ModuleFile, Env) ->
|
2011-05-23 11:46:03 +00:00
|
|
|
execute_plugin_hook("pre_", Command, Modules,
|
2012-02-07 19:15:58 +00:00
|
|
|
Config, ModuleFile, Env).
|
2011-05-23 11:46:03 +00:00
|
|
|
|
2012-02-07 19:15:58 +00:00
|
|
|
execute_post(Command, Modules, Config, ModuleFile, Env) ->
|
2011-05-23 11:46:03 +00:00
|
|
|
execute_plugin_hook("post_", Command, Modules,
|
2012-02-07 19:15:58 +00:00
|
|
|
Config, ModuleFile, Env).
|
2011-05-23 11:46:03 +00:00
|
|
|
|
2012-02-07 19:15:58 +00:00
|
|
|
execute_plugin_hook(Hook, Command, Modules, Config, ModuleFile, Env) ->
|
2011-05-23 11:46:03 +00:00
|
|
|
HookFunction = list_to_atom(Hook ++ atom_to_list(Command)),
|
2014-04-19 20:01:09 +00:00
|
|
|
execute(HookFunction, hook, Modules, Config, ModuleFile, Env).
|
2010-05-11 15:35:47 +00:00
|
|
|
|
2009-11-29 23:44:30 +00:00
|
|
|
%%
|
2010-06-09 19:16:58 +00:00
|
|
|
%% Execute a command across all applicable modules
|
2009-11-29 23:44:30 +00:00
|
|
|
%%
|
2012-02-07 19:15:58 +00:00
|
|
|
execute(Command, Modules, Config, ModuleFile, Env) ->
|
2014-04-19 20:01:09 +00:00
|
|
|
execute(Command, not_a_hook, Modules, Config, ModuleFile, Env).
|
|
|
|
|
|
|
|
execute(Command, Type, Modules, Config, ModuleFile, Env) ->
|
2009-12-12 14:34:29 +00:00
|
|
|
case select_modules(Modules, Command, []) of
|
2009-12-02 12:15:35 +00:00
|
|
|
[] ->
|
2014-04-19 20:01:09 +00:00
|
|
|
case Type of
|
|
|
|
hook ->
|
2011-07-06 19:22:04 +00:00
|
|
|
ok;
|
2014-04-19 20:01:09 +00:00
|
|
|
not_a_hook ->
|
2011-07-06 19:22:04 +00:00
|
|
|
?WARN("'~p' command does not apply to directory ~s\n",
|
|
|
|
[Command, rebar_utils:get_cwd()])
|
2012-04-22 19:53:32 +00:00
|
|
|
end,
|
|
|
|
Config;
|
2010-06-03 20:47:13 +00:00
|
|
|
|
2009-12-12 14:34:29 +00:00
|
|
|
TargetModules ->
|
2009-12-02 12:15:35 +00:00
|
|
|
%% Provide some info on where we are
|
2009-12-12 14:34:29 +00:00
|
|
|
Dir = rebar_utils:get_cwd(),
|
2009-12-02 12:15:35 +00:00
|
|
|
?CONSOLE("==> ~s (~s)\n", [filename:basename(Dir), Command]),
|
|
|
|
|
2012-04-22 19:53:32 +00:00
|
|
|
Config1 = increment_operations(Config),
|
2010-07-25 05:56:46 +00:00
|
|
|
|
2009-12-02 12:15:35 +00:00
|
|
|
%% Run the available modules
|
2012-04-22 19:53:32 +00:00
|
|
|
apply_hooks(pre_hooks, Config1, Command, Env),
|
2011-01-28 15:08:27 +00:00
|
|
|
case catch(run_modules(TargetModules, Command,
|
2012-04-22 19:53:32 +00:00
|
|
|
Config1, ModuleFile)) of
|
|
|
|
{ok, NewConfig} ->
|
|
|
|
apply_hooks(post_hooks, NewConfig, Command, Env),
|
|
|
|
NewConfig;
|
2009-12-03 16:41:10 +00:00
|
|
|
{error, failed} ->
|
2012-07-28 17:51:57 +00:00
|
|
|
?FAIL;
|
2010-10-28 04:31:35 +00:00
|
|
|
{Module, {error, _} = Other} ->
|
|
|
|
?ABORT("~p failed while processing ~s in module ~s: ~s\n",
|
2011-01-07 13:58:30 +00:00
|
|
|
[Command, Dir, Module,
|
|
|
|
io_lib:print(Other, 1, 80, -1)]);
|
2009-12-02 12:15:35 +00:00
|
|
|
Other ->
|
2010-10-28 04:31:35 +00:00
|
|
|
?ABORT("~p failed while processing ~s: ~s\n",
|
2011-01-07 13:58:30 +00:00
|
|
|
[Command, Dir, io_lib:print(Other, 1, 80, -1)])
|
2009-12-02 12:15:35 +00:00
|
|
|
end
|
2009-11-29 23:44:30 +00:00
|
|
|
end.
|
|
|
|
|
2011-12-12 18:08:40 +00:00
|
|
|
%% Increment the count of operations, since some module
|
|
|
|
%% responds to this command
|
2012-04-22 19:53:32 +00:00
|
|
|
increment_operations(Config) ->
|
|
|
|
Operations = get_operations(Config),
|
|
|
|
rebar_config:set_xconf(Config, operations, Operations + 1).
|
2011-12-12 18:08:40 +00:00
|
|
|
|
2012-04-22 19:53:32 +00:00
|
|
|
get_operations(Config) ->
|
2012-07-14 21:44:47 +00:00
|
|
|
rebar_config:get_xconf(Config, operations).
|
2009-12-30 12:13:39 +00:00
|
|
|
|
2009-12-12 14:34:29 +00:00
|
|
|
update_code_path(Config) ->
|
2010-06-09 19:16:58 +00:00
|
|
|
case rebar_config:get_local(Config, lib_dirs, []) of
|
2009-12-12 14:34:29 +00:00
|
|
|
[] ->
|
|
|
|
no_change;
|
|
|
|
Paths ->
|
|
|
|
LibPaths = expand_lib_dirs(Paths, rebar_utils:get_cwd(), []),
|
|
|
|
ok = code:add_pathsa(LibPaths),
|
Don't over-aggressively clean the code path in the presence of lib_dir directives
Rebar, when it encounters a lib_dir directive, caches the current code
path, adds the libdir(s) and returns the cached copy of the path. When
rebar has finished processing that directory, it restores the cached
path. This is problematic in the below scenario:
/(lib_dir)->G
A -> B -> C -> D -> E
\-> F -> D -> E
When rebar is finished processing B, it restores the code path to what
it was before it processed B, removing C, D, E and G from the code path.
This means when it comes to process F, neither D or E are in the code
path, so any header includes, rebar plugins or parse transforms will not
be in the code path. Without the lib_dir directive, rebar does no code
path cleanups, so everything works fine.
This change makes rebar only remove the explicit lib_dir code paths it
added and adds an inttest that replicates the above scenario.
2013-10-16 23:48:00 +00:00
|
|
|
%% track just the paths we added, so we can remove them without
|
|
|
|
%% removing other paths added by this dep
|
|
|
|
{added, LibPaths}
|
2009-12-12 14:34:29 +00:00
|
|
|
end.
|
|
|
|
|
|
|
|
restore_code_path(no_change) ->
|
|
|
|
ok;
|
Don't over-aggressively clean the code path in the presence of lib_dir directives
Rebar, when it encounters a lib_dir directive, caches the current code
path, adds the libdir(s) and returns the cached copy of the path. When
rebar has finished processing that directory, it restores the cached
path. This is problematic in the below scenario:
/(lib_dir)->G
A -> B -> C -> D -> E
\-> F -> D -> E
When rebar is finished processing B, it restores the code path to what
it was before it processed B, removing C, D, E and G from the code path.
This means when it comes to process F, neither D or E are in the code
path, so any header includes, rebar plugins or parse transforms will not
be in the code path. Without the lib_dir directive, rebar does no code
path cleanups, so everything works fine.
This change makes rebar only remove the explicit lib_dir code paths it
added and adds an inttest that replicates the above scenario.
2013-10-16 23:48:00 +00:00
|
|
|
restore_code_path({added, Paths}) ->
|
2011-01-07 16:24:27 +00:00
|
|
|
%% Verify that all of the paths still exist -- some dynamically
|
|
|
|
%% added paths can get blown away during clean.
|
2013-11-26 20:15:04 +00:00
|
|
|
_ = [code:del_path(F) || F <- Paths, erl_prim_loader_is_file(F)],
|
2009-12-12 14:34:29 +00:00
|
|
|
ok.
|
2009-12-30 12:13:39 +00:00
|
|
|
|
2012-08-09 14:15:10 +00:00
|
|
|
erl_prim_loader_is_file(File) ->
|
|
|
|
erl_prim_loader:read_file_info(File) =/= error.
|
2009-12-12 14:34:29 +00:00
|
|
|
|
|
|
|
expand_lib_dirs([], _Root, Acc) ->
|
|
|
|
Acc;
|
|
|
|
expand_lib_dirs([Dir | Rest], Root, Acc) ->
|
2010-10-01 12:37:42 +00:00
|
|
|
Apps = filelib:wildcard(filename:join([Dir, "*", "ebin"])),
|
2013-06-18 21:03:30 +00:00
|
|
|
FqApps = case filename:pathtype(Dir) of
|
|
|
|
absolute -> Apps;
|
2013-06-18 22:19:41 +00:00
|
|
|
_ -> [filename:join([Root, A]) || A <- Apps]
|
2013-06-18 21:03:30 +00:00
|
|
|
end,
|
2009-12-14 13:58:22 +00:00
|
|
|
expand_lib_dirs(Rest, Root, Acc ++ FqApps).
|
2009-12-02 03:34:18 +00:00
|
|
|
|
2009-11-29 23:44:30 +00:00
|
|
|
|
2009-12-02 12:15:35 +00:00
|
|
|
|
|
|
|
select_modules([], _Command, Acc) ->
|
|
|
|
lists:reverse(Acc);
|
|
|
|
select_modules([Module | Rest], Command, Acc) ->
|
2011-02-21 16:42:10 +00:00
|
|
|
{module, Module} = code:ensure_loaded(Module),
|
|
|
|
case erlang:function_exported(Module, Command, 2) of
|
2009-12-02 12:15:35 +00:00
|
|
|
true ->
|
|
|
|
select_modules(Rest, Command, [Module | Acc]);
|
|
|
|
false ->
|
|
|
|
select_modules(Rest, Command, Acc)
|
|
|
|
end.
|
|
|
|
|
2012-04-22 19:53:32 +00:00
|
|
|
run_modules([], _Command, Config, _File) ->
|
|
|
|
{ok, Config};
|
2009-11-29 23:44:30 +00:00
|
|
|
run_modules([Module | Rest], Command, Config, File) ->
|
2009-12-02 12:15:35 +00:00
|
|
|
case Module:Command(Config, File) of
|
2009-11-29 23:44:30 +00:00
|
|
|
ok ->
|
|
|
|
run_modules(Rest, Command, Config, File);
|
2012-04-22 19:53:32 +00:00
|
|
|
{ok, NewConfig} ->
|
|
|
|
run_modules(Rest, Command, NewConfig, File);
|
2010-10-25 22:38:51 +00:00
|
|
|
{error, _} = Error ->
|
2010-10-28 04:31:35 +00:00
|
|
|
{Module, Error}
|
2009-11-29 23:44:30 +00:00
|
|
|
end.
|
2009-12-12 14:34:29 +00:00
|
|
|
|
2014-02-20 09:56:37 +00:00
|
|
|
apply_hooks(Mode, Config, Command, Env0) ->
|
2011-03-12 09:32:58 +00:00
|
|
|
Hooks = rebar_config:get_local(Config, Mode, []),
|
2014-02-20 09:56:37 +00:00
|
|
|
Env = rebar_utils:patch_env(Config, Env0),
|
2011-03-12 09:32:58 +00:00
|
|
|
lists:foreach(fun apply_hook/1,
|
2011-12-04 17:29:11 +00:00
|
|
|
[{Env, Hook} || Hook <- Hooks,
|
|
|
|
element(1, Hook) =:= Command orelse
|
|
|
|
element(2, Hook) =:= Command]).
|
2011-01-26 01:50:33 +00:00
|
|
|
|
2011-12-04 17:29:11 +00:00
|
|
|
apply_hook({Env, {Arch, Command, Hook}}) ->
|
|
|
|
case rebar_utils:is_arch(Arch) of
|
|
|
|
true ->
|
|
|
|
apply_hook({Env, {Command, Hook}});
|
|
|
|
false ->
|
|
|
|
ok
|
|
|
|
end;
|
2011-04-05 14:04:03 +00:00
|
|
|
apply_hook({Env, {Command, Hook}}) ->
|
2011-01-26 01:50:33 +00:00
|
|
|
Msg = lists:flatten(io_lib:format("Command [~p] failed!~n", [Command])),
|
2011-04-05 14:04:03 +00:00
|
|
|
rebar_utils:sh(Hook, [{env, Env}, {abort_on_error, Msg}]).
|
|
|
|
|
|
|
|
setup_envs(Config, Modules) ->
|
2012-02-07 19:15:58 +00:00
|
|
|
lists:foldl(fun(M, {C,E}=T) ->
|
|
|
|
case erlang:function_exported(M, setup_env, 1) of
|
|
|
|
true ->
|
|
|
|
Env = M:setup_env(C),
|
2012-08-04 12:04:27 +00:00
|
|
|
C1 = rebar_config:save_env(C, M, Env),
|
2012-02-07 19:15:58 +00:00
|
|
|
{C1, E++Env};
|
|
|
|
false ->
|
|
|
|
T
|
|
|
|
end
|
|
|
|
end, {Config, []}, Modules).
|
2010-06-09 19:16:58 +00:00
|
|
|
|
2010-06-03 21:12:13 +00:00
|
|
|
acc_modules(Modules, Command, Config, File) ->
|
|
|
|
acc_modules(select_modules(Modules, Command, []),
|
|
|
|
Command, Config, File, []).
|
|
|
|
|
2012-04-22 19:53:32 +00:00
|
|
|
acc_modules([], _Command, Config, _File, Acc) ->
|
|
|
|
{Config, Acc};
|
2009-12-26 06:19:09 +00:00
|
|
|
acc_modules([Module | Rest], Command, Config, File, Acc) ->
|
2012-04-22 19:53:32 +00:00
|
|
|
{Config1, Dirs1} = case Module:Command(Config, File) of
|
|
|
|
{ok, Dirs} ->
|
|
|
|
{Config, Dirs};
|
|
|
|
{ok, NewConfig, Dirs} ->
|
|
|
|
{NewConfig, Dirs}
|
|
|
|
end,
|
|
|
|
acc_modules(Rest, Command, Config1, File, Acc ++ Dirs1).
|
2010-06-09 19:45:55 +00:00
|
|
|
|
|
|
|
%%
|
|
|
|
%% Return a flat list of rebar plugin modules.
|
|
|
|
%%
|
2012-12-08 21:07:10 +00:00
|
|
|
plugin_modules(Config, PredirsAssoc) ->
|
2011-08-16 15:34:09 +00:00
|
|
|
Modules = lists:flatten(rebar_config:get_all(Config, plugins)),
|
2013-11-27 14:12:46 +00:00
|
|
|
?DEBUG("Plugins requested while processing ~s: ~p~n",
|
|
|
|
[rebar_utils:get_cwd(), Modules]),
|
2012-12-08 21:07:10 +00:00
|
|
|
plugin_modules(Config, PredirsAssoc, ulist(Modules)).
|
2010-06-09 19:45:55 +00:00
|
|
|
|
|
|
|
ulist(L) ->
|
|
|
|
ulist(L, []).
|
|
|
|
|
|
|
|
ulist([], Acc) ->
|
|
|
|
lists:reverse(Acc);
|
|
|
|
ulist([H | T], Acc) ->
|
2010-06-19 08:08:34 +00:00
|
|
|
case lists:member(H, Acc) of
|
2010-06-09 19:45:55 +00:00
|
|
|
true ->
|
|
|
|
ulist(T, Acc);
|
|
|
|
false ->
|
|
|
|
ulist(T, [H | Acc])
|
|
|
|
end.
|
|
|
|
|
2012-12-08 21:07:10 +00:00
|
|
|
plugin_modules(_Config, _PredirsAssoc, []) ->
|
2010-06-09 19:45:55 +00:00
|
|
|
{ok, []};
|
2012-12-08 21:07:10 +00:00
|
|
|
plugin_modules(Config, PredirsAssoc, Modules) ->
|
2010-06-09 19:45:55 +00:00
|
|
|
FoundModules = [M || M <- Modules, code:which(M) =/= non_existing],
|
2012-12-08 21:07:10 +00:00
|
|
|
plugin_modules(Config, PredirsAssoc, FoundModules, Modules -- FoundModules).
|
2011-05-02 23:15:19 +00:00
|
|
|
|
2012-12-08 21:07:10 +00:00
|
|
|
plugin_modules(_Config, _PredirsAssoc, FoundModules, []) ->
|
2011-05-02 23:15:19 +00:00
|
|
|
{ok, FoundModules};
|
2012-12-08 21:07:10 +00:00
|
|
|
plugin_modules(Config, PredirsAssoc, FoundModules, MissingModules) ->
|
|
|
|
{Loaded, NotLoaded} = load_plugin_modules(Config, PredirsAssoc,
|
2012-06-08 19:56:18 +00:00
|
|
|
MissingModules),
|
2011-05-02 23:15:19 +00:00
|
|
|
AllViablePlugins = FoundModules ++ Loaded,
|
2011-08-25 14:13:16 +00:00
|
|
|
case NotLoaded =/= [] of
|
2010-06-09 19:45:55 +00:00
|
|
|
true ->
|
2012-06-08 19:56:18 +00:00
|
|
|
%% NB: we continue to ignore this situation, as did the
|
|
|
|
%% original code
|
2011-09-20 10:57:56 +00:00
|
|
|
?WARN("Missing plugins: ~p\n", [NotLoaded]);
|
2010-06-09 19:45:55 +00:00
|
|
|
false ->
|
2011-05-02 23:15:19 +00:00
|
|
|
?DEBUG("Loaded plugins: ~p~n", [AllViablePlugins]),
|
2010-06-09 19:45:55 +00:00
|
|
|
ok
|
|
|
|
end,
|
2011-05-02 23:15:19 +00:00
|
|
|
{ok, AllViablePlugins}.
|
|
|
|
|
2012-12-08 21:07:10 +00:00
|
|
|
load_plugin_modules(Config, PredirsAssoc, Modules) ->
|
2012-01-14 16:43:25 +00:00
|
|
|
Cwd = rebar_utils:get_cwd(),
|
2013-06-15 09:14:04 +00:00
|
|
|
PluginDirs = get_all_plugin_dirs(Config, Cwd, PredirsAssoc),
|
2013-11-27 14:12:46 +00:00
|
|
|
?DEBUG("Plugin dirs for ~s:~n~p~n", [Cwd, PluginDirs]),
|
2011-08-26 16:20:05 +00:00
|
|
|
|
2011-08-26 16:29:09 +00:00
|
|
|
%% Find relevant sources in base_dir and plugin_dir
|
2011-08-26 16:20:05 +00:00
|
|
|
Erls = string:join([atom_to_list(M)++"\\.erl" || M <- Modules], "|"),
|
2011-08-26 16:29:09 +00:00
|
|
|
RE = "^" ++ Erls ++ "\$",
|
2012-01-14 16:43:25 +00:00
|
|
|
%% If a plugin is found both in base_dir and plugin_dir, the clash
|
2011-08-26 16:29:09 +00:00
|
|
|
%% will provoke an error and we'll abort.
|
2013-05-15 22:56:45 +00:00
|
|
|
Sources = [rebar_utils:find_files(PD, RE, false) || PD <- PluginDirs],
|
2011-08-26 16:20:05 +00:00
|
|
|
|
|
|
|
%% Compile and load plugins
|
2013-05-15 22:56:45 +00:00
|
|
|
Loaded = [load_plugin(Src) || Src <- lists:append(Sources)],
|
2011-05-02 23:15:19 +00:00
|
|
|
FilterMissing = is_missing_plugin(Loaded),
|
|
|
|
NotLoaded = [V || V <- Modules, FilterMissing(V)],
|
|
|
|
{Loaded, NotLoaded}.
|
|
|
|
|
2013-06-15 09:14:04 +00:00
|
|
|
get_all_plugin_dirs(Config, Cwd, PredirsAssoc) ->
|
2013-11-27 14:12:46 +00:00
|
|
|
[rebar_utils:get_cwd()]
|
|
|
|
++ get_plugin_dir(Config, Cwd)
|
|
|
|
++ get_base_plugin_dirs(Cwd, PredirsAssoc).
|
2013-06-15 09:14:04 +00:00
|
|
|
|
|
|
|
get_plugin_dir(Config, Cwd) ->
|
|
|
|
case rebar_config:get_local(Config, plugin_dir, undefined) of
|
|
|
|
undefined ->
|
|
|
|
%% Plugin can be in the project's "plugins" folder
|
|
|
|
[filename:join(Cwd, "plugins")];
|
|
|
|
Dir ->
|
|
|
|
[Dir]
|
|
|
|
end.
|
|
|
|
|
|
|
|
%% We also want to include this case:
|
|
|
|
%% Plugin can be in "plugins" directory of the plugin base directory.
|
|
|
|
%% For example, Cwd depends on Plugin, and deps/Plugin/plugins/Plugin.erl
|
|
|
|
%% is the plugin.
|
|
|
|
get_base_plugin_dirs(Cwd, PredirsAssoc) ->
|
|
|
|
[filename:join(Dir, "plugins") ||
|
|
|
|
Dir <- get_plugin_base_dirs(Cwd, PredirsAssoc)].
|
|
|
|
|
2013-11-27 14:20:18 +00:00
|
|
|
%% @doc PredirsAssoc is a dictionary of plugindir -> 'parent' pairs.
|
2013-05-15 22:56:45 +00:00
|
|
|
%% 'parent' in this case depends on plugin; therefore we have to give
|
|
|
|
%% all plugins that Cwd ('parent' in this case) depends on.
|
|
|
|
get_plugin_base_dirs(Cwd, PredirsAssoc) ->
|
|
|
|
[PluginDir || {PluginDir, Master} <- dict:to_list(PredirsAssoc),
|
2013-06-15 09:14:04 +00:00
|
|
|
Master =:= Cwd].
|
2012-01-14 16:43:25 +00:00
|
|
|
|
2011-05-02 23:15:19 +00:00
|
|
|
is_missing_plugin(Loaded) ->
|
|
|
|
fun(Mod) -> not lists:member(Mod, Loaded) end.
|
|
|
|
|
|
|
|
load_plugin(Src) ->
|
|
|
|
case compile:file(Src, [binary, return_errors]) of
|
|
|
|
{ok, Mod, Bin} ->
|
|
|
|
load_plugin_module(Mod, Bin, Src);
|
|
|
|
{error, Errors, _Warnings} ->
|
|
|
|
?ABORT("Plugin ~s contains compilation errors: ~p~n",
|
|
|
|
[Src, Errors])
|
|
|
|
end.
|
|
|
|
|
|
|
|
load_plugin_module(Mod, Bin, Src) ->
|
|
|
|
case code:is_loaded(Mod) of
|
|
|
|
{file, Loaded} ->
|
|
|
|
?ABORT("Plugin ~p clashes with previously loaded module ~p~n",
|
|
|
|
[Mod, Loaded]);
|
|
|
|
false ->
|
|
|
|
?INFO("Loading plugin ~p from ~s~n", [Mod, Src]),
|
|
|
|
{module, Mod} = code:load_binary(Mod, Src, Bin),
|
|
|
|
Mod
|
|
|
|
end.
|