You do know that aggregation does not have to map with inheritance? You can have an aggregator pom that is not the parent of the projects it aggregates.
-Stephen On 6 April 2010 18:45, Marshall Schor <m...@schor.com> wrote: > > > On 4/3/2010 4:58 PM, Wayne Fay wrote: > >> I see this doc [1] says there is support in maven internally for > >> multiple parents, including both <parents> > >> > > Any particular reason you can't use multiple levels of parents... > > pom (grandparent) > > + pom (parent) > > ++ pom (child) > > > > Here's my use case. We have many (sub)projects, and several > aggregations of these into release "packages". The subprojects share > various common attributes, which I'd like to factor into parents, but > along different dimensions. > > For instance, some projects require a special extra build packaging step. > > Other projects (may overlap with above set) do their documentation using > docbook - and I want to factor out for those common settings of the > docbkx maven plugin. > > Because these sets of things are not in a hierarchical relationship, the > multiple-parent, or mixin style seems appropriate. I would add to those > projects using the extra packaging step, a mixin for that, and for those > using docbook style documentation, a mixin for that. > > -Marshall > > Wayne > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
