[
http://jira.codehaus.org/browse/MCLOVER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Gredler updated MCLOVER-69:
----------------------------------
Attachment: mclover-69.patch
We've been able to achieve this using the attached patch. In order to use it,
build and use a patched version of the clover plugin and add configuration like
the following to your pom.xml:
<reporting>
<plugins>
<plugin>
<artifactId>maven-clover-plugin</artifactId>
<configuration>
<reportExcludes>
<reportExclude>\*\*/client/framework/scanner/\*\*/\*.java</reportExclude>
<reportExclude>\*\*/client/testing/\*\*/\*.java</reportExclude>
<reportExclude>\*\*/shared/util/EqualsHashCodeTester\*.java</reportExclude>
<reportExclude>\*\*/ServerIntegrationApp.java</reportExclude>
</reportExcludes>
</configuration>
</plugin>
</plugins>
</reporting>
> Add support for excluding files when generating a report
> --------------------------------------------------------
>
> Key: MCLOVER-69
> URL: http://jira.codehaus.org/browse/MCLOVER-69
> Project: Maven 2.x Clover Plugin
> Issue Type: Improvement
> Affects Versions: 2.3
> Reporter: Brendan Humphreys
> Attachments: mclover-69.patch
>
>
> Hi,
> So that I can generate a report of a subset of the instrumented classes. This
> is different to using <exclude> at instrumentation time.
> Cheers,
> -Brendan
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
