I am new to maven. I am using maven 2.0.7. I have a multi-module project A which defines the dependencyManagement entries for the contained modules, say A1, A2, A3. But as suggested in books and sites I also have inheritance relation between the poms of the modules to the parent module, that is A's pom is parent of A1's, A2's and A3's poms. This works fine, but then it is not much of use since this grouping helps me only in building them together.
I have another project B that depends on this multi-module project A and I have declared a dependency of B on A with type=pom. Now this dependency is of no use since it is not adding the child modules to the classpath of this other project B. Neither does it allow me to add module-project dependencies without specifying their version. (That means i have to specify the version for each module, but then what's point of building them together as one project) I tried to fix this by adding child modules as dependencies of the top pom A, but this results in cyclic dependency problem because of inheritance relation. Am I missing something here or is it really a win-loss situation to mix these two features? -- View this message in context: http://www.nabble.com/pom-inheritence-and-multi-module-pom-do-not-complement-tf4119628s177.html#a11716184 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
