packaging/standalone: Include `rabbit` dependencies when creating the release script

Before this, this was working by chance because those dependencies were
brought by plugins. But if we build the package without any plugins, the
script complains about requires missing applications (kernel and
stdlib), and if we add hard-code them, it complains about other Erlang
applications not listed (sasl, mnesia, os_mon, ...).
This commit is contained in:
Jean-Sébastien Pédron 2017-10-17 19:02:28 +02:00
parent c571ef2cc3
commit cb7555f530
No known key found for this signature in database
GPG Key ID: 39E99761A5FD94CC
1 changed files with 4 additions and 2 deletions

View File

@ -54,8 +54,10 @@ start() ->
end, end,
%% we need a list of ERTS apps we need to ship with rabbit %% we need a list of ERTS apps we need to ship with rabbit
RabbitMQAppNames = [rabbit | [P#plugin.name || RabbitMQAppNames = lists:umerge(
P <- rabbit_plugins:list(PluginsDistDir, true)]] lists:sort(sets:to_list(expand_dependencies([rabbit]))),
[P#plugin.name ||
P <- rabbit_plugins:list(PluginsDistDir, true)])
-- PluginAppNames, -- PluginAppNames,
{ok, SslAppsConfig} = application:get_env(rabbit, ssl_apps), {ok, SslAppsConfig} = application:get_env(rabbit, ssl_apps),