ソースを参照

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

読み込み中…
キャンセル
保存