diff options
| author | Jean-Sebastien Pedron <jean-sebastien@rabbitmq.com> | 2014-11-24 20:40:21 +0100 |
|---|---|---|
| committer | Jean-Sebastien Pedron <jean-sebastien@rabbitmq.com> | 2014-11-24 20:40:21 +0100 |
| commit | 1963252daa89ff6736b2d4f776bcf6e9345db0b3 (patch) | |
| tree | 463fac68669a8db2839004fe37e59077c55faea7 /generate_deps | |
| parent | b9f9ba1e5e27e1b01df972be6ceb6cda47587138 (diff) | |
| download | rabbitmq-server-git-1963252daa89ff6736b2d4f776bcf6e9345db0b3.tar.gz | |
Add plugin paths to the beginning of the code path
The goal is to make sure the right application is picked, in case the
same one is available as both a RabbitMQ plugin and an external Erlang
application. For instance, this could be the case with the Cowboy
application: a version is available in the plugins, but the user could
add an incompatible version to Erlang/OTP libdir or set ERL_LIBS to
point to it.
There's one exception currently: eldap. This application used to be
available as a 3rd party one. But since Erlang R15B01, it's included
in the standard library. We trust this version to have a stable API.
Therefore, if the node runs on R15B01 or later and eldap version is
1.0+, we use this one. In all other cases, we don't trust it and prefer
the RabbitMQ plugin.
Diffstat (limited to 'generate_deps')
0 files changed, 0 insertions, 0 deletions
