-
Notifications
You must be signed in to change notification settings - Fork 114
Resolve interdependencies with rabbitmq-server #137
Comments
Just a note to say that in the management branch(es) I have already moved |
I will probably do the same as part of this issue. |
To clarify the scope of rabbitmq-common and this issue in particular, rabbitmq-common is used by:
For plugins, what is in rabbitmq-common vs. rabbitmq-server has little importance as they depend on the broker anyway. However, the Erlang client depends on rabbitmq-common only. Or more exactly, it should depend on it exclusively. Unfortunately, it also makes calls into the broker directly or indirectly through a reverse dependency in rabbitmq-common. Therefore, we must solve this issue from the Erlang client's point of view:
An example is |
…ories Modules which are not used by rabbitmq-common or rabbitmq-erlang-client are moved to rabbitmq-server. Modules which were in rabbitmq-server but were used in rabbitmq-common are moved to rabbitmq-common. References #137. [#118490793]
…ories Modules which are not used by rabbitmq-common or rabbitmq-erlang-client are moved to rabbitmq-server. Modules which were in rabbitmq-server but were used in rabbitmq-common are moved to rabbitmq-common. References rabbitmq/rabbitmq-common#137. [#118490793]
…ories Modules which are not used by rabbitmq-common or rabbitmq-erlang-client are moved to rabbitmq-server. Modules which were in rabbitmq-server but were used in rabbitmq-common are moved to rabbitmq-common. References #137. [#118490793]
…ories Modules which are not used by rabbitmq-common or rabbitmq-erlang-client are moved to rabbitmq-server. Modules which were in rabbitmq-server but were used in rabbitmq-common are moved to rabbitmq-common. References rabbitmq/rabbitmq-common#137. [#118490793]
Dependency circles between the broker, the client and rabbitmq-common were fixed in 3.6.x and 3.7.x. |
Currently, there are many calls from modules in rabbitmq-common to modules in rabbitmq-server. The first problem was fixed in rabbitmq/rabbitmq-server#980. We still have the following incorrect calls:
Thus we need to move modules between both applications and probably need to rewrite a few things.
The text was updated successfully, but these errors were encountered: