Hi Vincent,
it is quite common to use POM inheritance defining the reports and use a few exceptions :
+) in fulcrum-cache there is a seperate report section to avoid the JCoverage plugin during the long running tests since it uses POM inheritance. And it drives me nuts that I have to disable my broken SIMIAN report in two project.xml
+) for one of my customers I also have to redefine the reports since it would measure tons of Torque-generated code while I'm only interested that the connectivity and accessing all tables works
I think the question is not necesarry if it is already possible but if it is in general sensible to turn off a report using a property .... :-)
Thanks in advance
Siegfried Goeschl
Vincent Massol (JIRA) wrote:
[ http://jira.codehaus.org/browse/MPCLOVER-33?page=history ]
Vincent Massol closed MPCLOVER-33:
----------------------------------
Resolution: Won't Fix Assign To: Vincent Massol
Closing as it's already possible to do this by not adding the clover report to the project who don't want it...
There should be a property to turn off Clover ---------------------------------------------
Key: MPCLOVER-33
URL: http://jira.codehaus.org/browse/MPCLOVER-33
Project: maven-clover-plugin
Type: Improvement
Environment: Maven 1.0.2
Reporter: Wim Deblauwe
Assignee: Vincent Massol
It would be convenient to have a property (e.g. maven.clover.enabled) to turn Clover on or off. This is especially handy when using Clover with the multiproject plugin when some of the projects are not java projects.
