> -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: lundi 27 mars 2006 18:12 > To: 'Maven Developers List' > Subject: Issues while trying to implement an aggregated report for the > Clover plugin > > Hi, > > As I mentioned in some previous email, I'm trying to implement a use case > for the Clover plugin where a multimodule build will aggregate all Clover > databases to generate a consolidated report. I'm facing some issues: > > 1) How to execute the aggregated report as the last step in the > multimodule build? Right now the top level module build is done before the > rest and thus the clover dbs are not created yet...
I think I solved this one by using the @aggregator tag. I have something working that I have just committed: when run as part of a multimodule build, running mvn site will generate an aggregated report in addition to generating individual reports in each module. > 2) Problem of accessing plugin configuration data. See > http://jira.codehaus.org/browse/MNG-2180 Kenney suggested to reparse the pom. I'll have a look at how it's done in the Eclipse plugin. Right now, I have assumed that the location of the clover databases is the same as the location defined in the parent. > 3) Problem of having multiple reports in one plugin. In this case one > report needs forking a custom lifecycle while the other must not fork a > lifecycle. Still no idea how to handle this one. Seems we need the same executions mechanism for report plugins that we have for build plugins. WDYT? Thanks -Vincent ___________________________________________________________________________ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
