diff options
| author | Jean-Sébastien Pédron <jean-sebastien@rabbitmq.com> | 2020-01-24 11:37:50 +0100 |
|---|---|---|
| committer | Jean-Sébastien Pédron <jean-sebastien@rabbitmq.com> | 2020-01-24 11:43:58 +0100 |
| commit | ba1b6cbbfe24715d98eac5a6c97e199db137c76d (patch) | |
| tree | d4b9ea9e5e6f23d98a5588e0534b7d9bf9f98a6a /scripts | |
| parent | dd8262646d208e394844e26edbc1fec47949129d (diff) | |
| download | rabbitmq-server-git-ba1b6cbbfe24715d98eac5a6c97e199db137c76d.tar.gz | |
rabbit: Fix plugins' run_boot_steps() vs. start order
Before `rabbit` startup code was rewritten as part of
rabbitmq/rabbitmq-server#2180 to make it closer to a regular Erlang
application, plugins' boot steps were executed before plugins were
started.
This commit restores this behavior. Indeed the initial patch inverted
them by starting the plugins first, then executed the boot steps.
It also brings another improvement in the process: a dependency has its
boot steps executed and is started before a plugin which depends on it
is considered. This should improve consistency.
Note that the `start_apps/2` function, which is run when a user enables
a plugin at runtime must be improved as well. There is a work in
progress in rabbitmq/rabbitmq-server#2219.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions