Closed
Description
I have a release that consists of two applications. I need one of the applications ('appenv') to start before all the dependencies of the second ('reporter').
This is how relx used to generate the boot script. E.g. in relx 3.21.1 (rebar3 3.3.2) it would start appenv before the dependencies of reporter, but in relx 3.22.2 (rebar3 3.3.5) it doesn't.
Is this a bug or a feature? If it is intended bahaviour, how am I supposed to specify that an app should start first?
{relx, [{release, {reporter, {semver,""}}, [appenv, reporter]},
rebar 3.3.2 on Erlang/OTP 18 Erts 7.3
{progress,applications_loaded},
{apply,{application,start_boot,[kernel,permanent]}},
{apply,{application,start_boot,[stdlib,permanent]}},
{apply,{application,start_boot,[appenv,permanent]}},
...
{apply,{application,start_boot,[reporter,permanent]}},
{apply,{c,erlangrc,[]}},
{progress,started}]}.
rebar 3.3.5 on Erlang/OTP 18 Erts 7.3
{progress,applications_loaded},
{apply,{application,start_boot,[erlang_localtime,permanent]}},
{apply,{application,start_boot,[kernel,permanent]}},
{apply,{application,start_boot,[stdlib,permanent]}},
...
{apply,{application,start_boot,[appenv,permanent]}},
{apply,{application,start_boot,[reporter,permanent]}},
{apply,{c,erlangrc,[]}},
{progress,started}]}.
Metadata
Metadata
Assignees
Labels
No labels