Unloaded Modules and Maven dependencies

Hi,

I have tested first time with "unloaded modules".

If I am working on Module A which is a Maven Project, I can define Module B as a Maven dependency and everything works. Sadly, if I have to develop on both modules, whenever I do something in B, I have to "mvn install" B and reload in A.

So, I tested to load Module B into my Project of Module A. Now I can change anything in Module B and I can directly see my changes in Module A. Super!

Ok, now I want to unload Module B for a while, because everything works fine in B. IntelliJ reminds me that it is used by Module A. I don't consider, because I think IntelliJ will then use the Maven dependency instead... => FAIL

Why?

I thought I could add all into my project and just load only those modules without keeping dependencies in mind, cause Maven is doing the rest.

Even a "Maven reload" doesn't work". IntelliJ seems to perceive that there is an unloaded(!) module and ignores the Maven dependency... :(

Is there a way to solve this problem?
(My real scenario is much more complex where Module A and Module B is a multi-module project and there is also a Module C, D, ....)

BR,

Michael