I'm not happy with the current aggregation support in reports. For
Javadoc I did it by a flag to allow the same report to work for both
single and multi-module projects (if in root and aggregate on, iterate
through the reactor projects and generate as an aggregate, if not in the
root don't generate anything).
If it were a separate report, @aggregate would essentially do the same
job without the config trickery.
However, we really need to consider better use cases, as attempting to
aggregate the clover report has shown. This one should be doable.
Cheers,
Brett
Mike Perham wrote:
I'm trying to build an aggregating version of the JavaNCSS report. We
have 30-40 modules but don't want to mine those reports by hand for
totals.
The issue is simply one of ordering: when I generate the top-level site,
it runs my aggregating report BEFORE the child reports. My report is
generated based on the information in the child project reports. Is it
possible to run a report AFTER the children have generated? Of course
now you need to change the deployment process, etc.
Attached is an example of what I have so far.
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
