Hi, We have the following project structure
A + B ( packaging type jar ) + C + D Where D has a dependency on B. The packaging type for 'A' is set as 'pom' and B, C and D are configured as modules. In addition, the poms in B, C and D also refer to A's pom through the parent element. If I understand this, the former ensures aggregation kicks-in and the latter ensures that child poms inherit stuff from the parent pom. Now when I run mvn package from within A, when the dependencies are resolved for 'D', the dependency on B is resolved by including the B\target\B.jar jar file. However, when I run the package from within D, the dependency on B is resolved from the local repository. Why doesn't maven detect that D is a sub module of the aggregation in 'A'. It manages to get to the A pom, so it might as well see that D is part of A's aggregation and then resolve the dependencies as per aggregation ? Is there way to do achieve this ? Thanks, Rk
