Isn't that what the aggregate parameter is for in individual report mojo's? They have a check: if aggregrate = true, and the current project is not the reactor root, they skip the build. If not, they generate the report using data from the reactor projects.
AFAIK parent projects are executed _after_ the modules anyway. So this comes down to report plugins supporting aggregation themselves, right? Mike Perham wrote:
There's a case (aggregating reports) where it would be useful to have a parent project's site generate AFTER the children's site is generated. Would it be possible and/or easy to add an report lifecycle event which is called on the parent reports after the children are processed? mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
