maven site lifecycle

[Mike Perham <mp...@gmail.com>]

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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: maven site lifecycle

[Mike Perham <mp...@gmail.com>]

My understanding was the opposite.  I thought that reports that
support aggregate run the child reports themselves so they can get the
data to aggregate because the site lifecycle does not support it.  Am
I misunderstanding it?

I'm pretty sure parent reports run first but I'd like to hear evidence
to the contrary.

On 1/9/07, Kenney Westerhof <ke...@apache.org> wrote:
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: maven site lifecycle

[Kenney Westerhof <ke...@apache.org>]

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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org