Yes, everything that implements MavenReport is a report in the plugin. Bear in mind that when someone configures the plugin, they usually don't specify one report or the other, so they are *all* run.
You probably don't want that. What I'd suggest instead is having the one report with configuration to modify behaviour. Specifically for the aggregation case - take a look at JXR/Javadoc that I added yesterday. When you put <aggregate> as configuration, it gathers it all up at the top, then skips generation in the modules. Its probably different for clover, because it has to run the tests across them all, then aggregate later. - Brett Vincent Massol wrote: > Hi, > > I'm working on the Clover plugin and I have a need for 3 reports: > > * one that runs the full stuff in a forked lifecycle (instrumentation, > executing tests and generating a Clover report). This is what the current > clover:clover mojo does. > > * one that takes a Clover database and simply generates a report out of it. > This could also be an aggregator that finds all the clover databases in > modules and aggregate them. > > Is it possible to have several reports in the same plugin? > > Thanks > -Vincent > > > --------------------------------------------------------------------- > 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]
