This isn't the first attempt actually - from what I understand multiproject's dependency convergence report is an aggregator.
The way I think it should work is: 1) all reports are per project (including depencency convergence!) 2) multiproject provides a generic aggregation utility to pull down multiple result files. 3) reports are then run over the aggregated files as they would for any other project, as they should be in the same format. To implement this, I guess each "aggreator compliant" plugin needs to provide a way to merge two output files - so you instruct junitreport to merge target/TESTS-AllSuites.xml, subproject1/target/TESTS-AllSuites.xml, etc, into one target/TESTS-AllSuites.xml, which is then transformed as usual by the report plugin. Checkstyle, dashboard, changes, could all do the same. There would need to be a way to exclude certain reports from being aggregated - eg checkstyle might be far too large in some cases to want to aggregate, and "changelog" and the other CVS reports should only be aggregated when the subprojects are not underneath the same CVS module (if they are, the base directory one is effectively already aggregated). What do you guys think? I think this is a powerful feature and something I've thought about before - probably best to have a decent go at solving the problem than introducing something different for each report. Cheers, Brett > -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 11 November 2003 7:46 AM > To: Maven Developers List > Subject: RE: [changes] New goal for release report! > > > You're making the first attempt so what do you think would be > easier for the user and for maintenance down the road? >
