hooks/artifacts are always run/resolved from an app unless at top of umbrella #779
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All hooks will be run as part of the
app_info
set of hooks, incompile
for example: https://github.com/rebar/rebar3/blob/master/src/rebar_prv_compile.erl#L87 and artifacts will be found relative to an app's output directory, except in the case of being defined in the rebar.config at the top level of an umbrella project. In that case artifacts will be resolved fromprofile_dir
(eg_build/default/
) and hooks will be run from the top level before any part of a provider is run, like https://github.com/rebar/rebar3/blob/master/src/rebar_prv_compile.erl#L49Additionally 3 variable can be used in the artifacts string:
base_dir
,profile_dir
orout_dir
--out_dir
is the default path to start finding artifacts but I figured it would be nice to let it be explicit as well, example:{artifacts, ["{{out_dir}}/priv/eleveldb.so"]}.