I'm using IDEA 7.0.3 with some Maven 2 projects.
We have a number of modules, all configured with Maven 2. Until now, I'd created a project in IDEA, then imported each pom individually, then configured the dependencies between them. For example, say we have a Maven module "frontend" and a Maven module "shared". Frontend depends on shared and imports some reusable classes from it. I'd configured the project so that the IDEA module "frontend" depended on the IDEA module "shared". By default, on loading from the POM, the IDEA module "frontend" would depend on the jars for shared, but not link the modules.
Note that in the POM for frontend, it declares shared (a version of it) as a dependency. Shared is a common module declared as a dependency for many modules in our system; it's not a Maven sub-module for, say, frontend.
This is all OK, but I was dreading synchronizing the Maven projects anymore to pick up dependencies, since at least in some previous attempts this seemed to wipe out the inter-module (IDEA module) dependencies. So today I decided to try a new tack, and created a "super POM" which lists all the top-level Maven modules in our system as sub-modules. I then opened that POM in IDEA. Worked great--I have all my modules available.
IDEA doesn't pick up the relationship between the modules, say between frontend and shared. The question is if there is any way to get IDEA to figure this out automatically without me having to replace the (many) dependencies declared as JARs in each module with an IDEA module dependency. That is, by default the IDEA frontend module depends on shared-0.9.jar instead of the IDEA module for shared.
Hope this makes sense :).
What I then decided to