浏览代码

Name the app being escriptize

Since the compiler refactor changed the order of steps and all hooks get
applied at once, knowing which app is being escriptized isn't really
obvious, particularly when many apps individually define their own 'main
app' and they get run at once.

This adds the name of the main app being run when escriptizing it to make
it clear what goes on, especially if there are failures.

This was reported in https://github.com/erlang/rebar3/pull/2211#issuecomment-615937628
pull/2288/head
Fred Hebert 5 年前
父节点
当前提交
0b3f216b19
共有 1 个文件被更改,包括 1 次插入1 次删除
  1. +1
    -1
      src/rebar_prv_escriptize.erl

+ 1
- 1
src/rebar_prv_escriptize.erl 查看文件

@ -85,7 +85,7 @@ do(State) ->
Err;
_ ->
AppInfo1 = rebar_hooks:run_all_hooks(Cwd, pre, ?PROVIDER, Providers, AppInfo0, State),
?INFO("Building escript...", []),
?INFO("Building escript for ~s...", [rebar_app_info:name(AppInfo0)]),
Res = escriptize(State, AppInfo1),
rebar_hooks:run_all_hooks(Cwd, post, ?PROVIDER, Providers, AppInfo1, State),
Res

正在加载...
取消
保存