title: Erlang / Rebar3 - How to add an application to release but not launch it?
body: <p>I have an umbrella project, includes main_app, app1, app2. main_app can work singe, or can work with and manage app1 and app2.</p>
  <p>The decision about the launching of app1 and app2 is on external side (special config file, filled by a user).</p>
  <p>I use rebar.config, part of it:</p>
  <pre><code>{lib_dirs, [&quot;apps&quot;]}.
  {sub_dirs, [
    &quot;apps/main_app&quot;,
    &quot;apps/app1&quot;,
    &quot;apps/app2&quot;
  ]}.
  
  {relx, [{release, {main_app, &quot;0.8.6&quot;},
           [kernel,
            sasl,
            main_app]},
          {sys_config,  &quot;./config/sys.config&quot;},
          {vm_args,     &quot;./config/vm.args&quot;},
          {dev_mode, true},
          {include_src, true},
          {include_erts, false},
          {extended_start_script, true}]
  }.
  
  {profiles, [
    {prod, [
      {relx, [
        {dev_mode, false},
        {include_erts, false},
        {include_src, false},
        {sys_config,  &quot;./config/prod_sys.config&quot;},
        {vm_args,     &quot;./config/prod_vm.args&quot;}
      ]}
    ]}
  ]}.
  </code></pre>
  <p>If I use <code>sudo rebar3 shell</code> - I can manage app1 and app2.
  But if I pack a release by <code>sudo rebar3 as prod tar</code> - I get a tar archive which does not include beam files of app1 and app2.
  I know, if I put app1 and app2 to release section in the list with <code>kernel, sasl, main_app</code> - my needed apps will be added to release, but they will be automatically launched (I need to launch by myself)!</p>
  <p>How to configure rebar for adding all the libraries or applications to tar release, but not to launch them during starting main_app?</p>
  <p>Thanks in advance!</p>