Cyclic dependency after adding ApplicationModuleListener

[lennert-vanwaeleghem]

Context:

• I have two modules, let's call them moduleA and moduleB.
• moduleB uses moduleA (ApiInterface exposed on the root of moduleA, implemented in moduleA)
• moduleA is supposed to listen to an event from moduleB through an ApplicationModuleListener

Now the problem arises that there's a cyclic depedency introduced even though all moduleA does is listen to an event from moduleB even when ModuleA is not using or depending on moduleB. Listening on an event from another module should not introduce a cyclic dependency in my opinion.

I found 3 possible ways to avoid this:

1. moduleB has an ApplicationModuleListener on it's own event and calls a method on the moduleA ApiInterface to let moduleA handle it
2. introduce a "shared" module and move the ApiInterface and maybe some other future ApiInterfaces / from moduleA in there. That way moduleB uses the "shared" module, and moduleA listens to the event from moduleB.
3. introduce an eventInterface on moduleA for moduleA to listen to, with the implementation being the actual event in moduleB

What would be the best course of action here? Am I missing a 4th option maybe?