Yes, me too. i try to develop the same plugin and i have the problem.
If i put my report at the end of plugins list in <reporting> section, it works for 1 project but doesn't work for projects with module. see my last posts : http://www.nabble.com/-m2--Dashboard-report-plugin-tf2338270.html#a6506403 or http://www.nabble.com/-m2--lifecycle-design-tf2350045.html the only one solution is to declare plugin in <reporting> section: with this you have the item menu in the generated site and re-generated your dashboard after site generation as : mvn compile site dashboard-report:report if your plugin is "dashboard-report" with goal "report" as i do it's the the same problem as Clover plugin as described in JIRA: http://jira.codehaus.org/browse/MNG-2184 J.J.B. Rentrop wrote: > > It's good to hear that there is someone who is also working on it. I'm > in favour of focusing the work and have this available for everyone. > > Your solution works for projects that have packaging="jar" but not for > projects that consists of multiple modules (packaging="pom"). It can > affect the sequence of the plugins that are ran for each site but it > can't make the plugin execute after the site phase for each module has > been executed. > > Best regards, > Julien > > ----- Original Message ----- > From: Gisbert Amm <[EMAIL PROTECTED]> > Date: Thursday, October 19, 2006 12:17 pm > Subject: Re: Aggregate plugin that runs after each module's reports > To: Maven Users List <[email protected]> > >> I'm currently writing almost the same plugin, formerly (in the >> Maven 1 >> world) known as "Dashboard Plugin". Isn't that funny (I think it >> isn't)? >> Would it probably not be better to focus such efforts within the >> Maven >> project itself rather than having each company writing it's own >> Dashboard plugin for Maven 2? >> >> Your question: I simply wrote the <plugin> section for this plugin >> behind all others in the POM and that seems to work. Of course, one >> has >> to check if the required XML lies there as expected. ATM, I'm >> simply >> leaving the respective table cells in the generated report empty if >> that >> should happen. >> >> -Gisbert >> >> J.J.B. Rentrop wrote: >> > Hi all, >> > >> > I'm looking for ways to enable an aggregate report for multi module >> > projects for tools like checkstyle, cobertura, findbugs, surefire >> etc.> >> > One approach I'm trying is to first generate all reports and xml >> data> files for each module and afterwards loop through each >> module, read >> > their xml output file and create an aggregation report based on >> that data. >> > >> > The problem I face is that my aggregation MavenReport executes >> before> the reports of each modules has been executed. When I run >> "mvn site" it >> > will create an empty aggregate report, because it's unable to >> gather the >> > data from each module. If I run it a second time it will work >> because> then the data files of each module are available. >> > >> > Is there a way to make my aggregation MavenReport execute after the >> > reports of all modules have been generated? I have tried some >> > annotations but it didn't work. >> >> -------------------------------------------------------------------- >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Aggregate-plugin-that-runs-after-each-module%27s-reports-tf2472384.html#a6894274 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
