Quoting John Casey <[EMAIL PROTECTED]>: > Do you have even more plugin configuration in this third parent POM? If not, > why is it critical that the webapp/library projects can declare themselves > to be children of this POM (in addition to the type-specific POMs)? If you > do have more plugin configuration in this coordinating parent POM, why is it > not maintained in the type-specific POMs, or even further up the chain in a > common parent of those two parent POMs?
That's what I currently do and it confuses the site plugin. The site plugin has to determine which projects are "children" or another. Here is the directory tree: root +--parent-pom +--library-pom +--webapp-pom +--lib1 +--p2 +--lib2 +--webapp2 POM inheritance: parent-pom +--library-pom | +--lib1 | +--lib2 +--webapp-pom | +--webapp2 +--p2 So when the site plugin builds "p2" does it have children or not? How should it link to lib2 and webapp2? From the parent POM or the pom.xml in the parent directory? I think that other plugins are also affected because I see that Maven is printing some messages when I have ../pom.xml and <parent> in a project. That sparked the idea of having mixins. With mixins, I could separate the two trees cleanly. Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://www.philmann-dark.de/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
