> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: mercredi 29 mars 2006 06:45 > To: Maven Developers List > Subject: Re: Issues while trying to implement an aggregated report for the > Clover plugin
[snip] > >> 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? > > We do. It's reportSets. The default is to execute *all* though, where in > <build> the default is to run *none*. Ok, I hadn't realized this. Thanks for the info. However this will not work as the default is to execute all reports. I've opened a jira issue for this: http://jira.codehaus.org/browse/MNG-2193 In other words, this use case (http://jira.codehaus.org/browse/MCLOVER-19) cannot be implemented before MNG-2193 is fixed... 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]
