summaryrefslogtreecommitdiff
path: root/src/app_utils.erl
Commit message (Collapse)AuthorAgeFilesLines
* Fix await_startup/1. Change its design from "figure out what apps we should ↵bug26295Simon MacMullen2014-07-211-13/+1
| | | | be running and wait for them" to "wait for the boot marker to go away".
* If we refactor rabbit_misc:build_acyclic_graph so that we don't assume the ↵Simon MacMullen2014-03-191-2/+2
| | | | arity of the functions we pass in, then it's easy to build the complete graph then filter it by application, rather than the other way round - avoiding rather a lot of work.
* Get rid of app_utils:app_modules/1Tim Watson2014-03-181-6/+1
|
* Merge default into bug24926Tim Watson2014-03-181-1/+7
|\
| * Refactor (inline a little bit more)Tim Watson2014-03-171-6/+1
| | | | | | | | | | app_utils:which_applications/0 => inlined, rabbit_misc:all_module_attributes{_with_app} => unified
| * Inline app_utils:update_running_apps/2Tim Watson2014-03-171-11/+1
| |
| * Reduce the distance to default a bit moreTim Watson2014-03-041-2/+2
| |
| * Publish plugin changes via rabbit_eventTim Watson2014-03-031-1/+21
| |
| * Cosmetic - reduce the distance to default a bit moreTim Watson2014-02-211-3/+3
| |
| * Refactor - remove unused functions/comments/todosTim Watson2014-01-121-4/+1
| |
| * Refactor (simplify application stop handling)Tim Watson2014-01-121-36/+0
| | | | | | | | | | | | | | | | | | | | | | The offline plugin handling does a fine job of detecting which apps need to be stopped/unloaded when disabling a plugin at runtime. We previously had problems accidentally stopping things like stdlib and mnesia by accident, but only because we went searching for the app dependencies ourselves! Instead, we stop only those applications (i.e., plugins) that rabbit_plugins_main has requested. In doing so, we remove a considerable amount of (new) digraph hacking from app_utils and reduce the complexity of rabbit_boot somewhat.
| * refactor (renaming)Tim Watson2013-11-261-3/+3
| |
| * De-duplicate dependency/graph building functionsTim Watson2013-11-261-18/+13
| |
| * Re-work boot step handlingTim Watson2013-11-211-10/+6
| | | | | | | | | | | | | | | | | | We need to support interleaving plugin boot steps with rabbit?s own (internal) ones during the boot/start sequence, and also running them independently during runtime activation. This commit also drops the use of an ets table to track which cleanup steps we?ve run, and simplifies the boot step execution procedures.
| * Various boot procedure improvementsTim Watson2013-11-201-0/+36
| | | | | | | | | | | | We ensure that all dependent applications are stopped, but also that dependencies shared by multiple applications (e.g., amqp_client) are not.
| * Rework boot step handlingTim Watson2013-11-181-1/+4
| |
| * Restructure our boot procedure for more flexible boot-step handlingTim Watson2013-11-051-5/+15
| |
* | Update copyright for 2014bug25940Simon MacMullen2014-03-171-1/+1
|/
* s/VMware/GoPivotal/gSimon MacMullen2013-07-011-2/+2
|
* graceful handling of application:which_applications() timeoutbug25571Matthias Radestock2013-05-311-1/+1
|
* Update copyright 2013bug25343Emile Joubert2013-01-231-1/+1
|
* Variant of {start,stop}_applications that takes an error handler.Simon MacMullen2012-09-141-12/+29
|
* rabbitmqctl uses rabbit:await_startup/0Tim Watson2012-05-091-2/+14
|
* migrate application handling code to app_utilsTim Watson2012-05-091-0/+109