On Wed, Jul 20, 2011 at 8:14 AM, kanesee <kane...@gmail.com> wrote: > So it seems Maven handles dependency inheritance pretty well. > Let's say I have a parent project A that depends on projects B and C. And > both B and C depend on D. This works fine as dependencies. > > But suppose I wanted to make B and C modules of A. And I want to make D a > module of B and C, then Maven will complain that two or more projects in the > reactor have the same identifier. I believe this is because module D is > included twice. > > Does anyone know how to get around this? > ...perhaps some need plugin that ignores this duplicate identifier?
Modules do not equal inheritance. Think of modules as syntactic sugar to allow you to run a class at the top level and have maven automatically run the same command for all modules. Just because B is a module of A does not mean that B depends upon anything in A. Also remember that if a pom contains a module then its pom/type should always be "pom" (and not jar, ear, war, etc) Can you explain what you are attempting to achieve with this dual module inclusion? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
