Vincent Massol Emmanuel Venisse Add support for span attribute. Allow to specify the "relative" property for clover-setup. Upgrade to Clover 1.3.11. Use new clover license. Allow override of flushpolicy, flushinterval in <clover-setup>, change default values. Upgrade to Clover 1.3.9. The ant:clover-checkAnt task requires initStringparameter. When calling clover:ona second time, an updated maven.compile.src.setwas ignored. Fixed the clover:test-singlegoal which was wrongly calling the clover:swing-report-internal(should have been clover:swing-report). Fixed bug when maven.test.failure.ignoreis null. maven.test.failure.ignoreis now correctly reset when clover:offis called. Fully disable Clover in clover:offso that the Clover compiler adapter delegates straight to the default compiler. Removed the maven.clover.jarproperty that was used to override the default Clover jar. This property was not working (it requires Ant 1.6) and is no needed anymore as Cenqua has cleanly separated the Clover jar from the Clover license. You only need to point maven.clover.license.pathto your license file. Added a quick usage guide in the documentation. Fixed issue where clover:reportwas not calling clover:onleading to an error when generating the reports. Ensure that clover:init, clover:onand clover:offcan only be called once. For example calling clover:ontwice in a row will execute it only once. The clover:*-reportgoals do not call clover:testanymore. They only generates Clover reports. This is now aligned with the clover:reportbehavior. To run the full thing, execute the clovergoal or add the Clover report to your project's POM. Added a maven.clover.multiprojectproperty that should be set to true in your master project (if you're using a multiproject setup). Setting it to true will make the clovergoal and the maven-clover-pluginreport in your POM execute on all subprojects (they'll call the new clover:multiprojectgoal). New clover:multiprojectgoal to run Clover on a multiproject setup. New clover:mergegoal that creates a new Clover database by merging several other databases specified using the maven.clover.merge.databasesproperty (which defaults to **/clover_coverage.db). Fixed issue with Clover task and type definitions not using an explicit classpath which apparently breaks under Maven 1.1. Always generate Clover reports even when there is no coverage data. One of the reason is that Clover generates metrics other than coverage percentage, like LOC and NCLOC which are useful in themselves. Upgraded to Clover 1.3.6 Added PDF report generation. Added support for historical reports by adding a new clover:save-historygoal that saves a Clover history point. The history points are then used by clover:reportto generate history reports (including a link on the Maven-generated website). Updated to Clover 1.3.5 and applied new license that supports generating history report (the previous one didn't support it). Add support for method, statement and block context filtering through the following properties: maven.clover.context.block.names, maven.clover.context.method.names, maven.clover.context.method.regexps, maven.clover.context.statement.namesand maven.clover.context.statement.regexps. Added new clover:checkgoal that verifies if the test coverage if above a threshold defined by the properties maven.clover.check.target, maven.clover.check.packagesand maven.clover.check.targets. It fails the build if it's below. Changed the location of the default license. It is now bundled in the plugin and the plugin no longer downloads it from your remote repository. As before if you wish to use your own license use the maven.clover.license.pathproperty. Do not create a Clover report link when the project has no tests. Open Clover report page in a new window in the same manner as it's done for the Javadoc and XRef reports. Added maven.clover.includesand maven.clover.excludesproperties to specify what files to include/exclude from the Cloverification. Added new maven.clover.execute.during.reportproperty to control whether or not the clover-reportgoal builds Cloverify the sources and execute the tests (defaults to true). Deprecated maven.clover.database.dirproperty and replaced it with a maven.cover.databaseproperty that contains not only the database directory but also the name of the database file. clover:offshould now reset correctly the maven.build.destproperty that clover:onmodifies. Note that the reported error has been fixed even though I have not been able to reproduce the problem (and hence we don't have a test for it). Upgraded Clover to version 1.3.4. The default compiler was not reset after the execution of the clover:reportgoal. Added ability for users to specify their own Clover license file by overriding the new maven.clover.license.pathproperty. Made the following goals public by documenting them: clover:report, clover:on, clover:off, clover:test, clover:test-single. Added new clover:test-singlegoal to execute a single test case and to view the test coverage result directly using the Clover Swing viewer. This is useful if you wish to quickly see the action that a single unit test has on the code it tests. Now using maven:getand maven:set. The clover:reportgoal does not call the tests anymore. It only generates Clover reports. When executing clover:onand clover:off, modify the maven.build.destproperty value in the Root context of all plugins so that the value change is available in all Maven plugins. Prevented the clover:ongoal from failing when there are no unit tests sources available. Updated to Clover Ant 1.3_01. Do not execute Clover if there are no tests to run Clover on. This prevents an error happening in the clover:ongoal. Allow generating XML and/or Swing reports during the web site generation too. Tests executed after <clover:onare now always forked. Allows the user to override the Clover jar. This is especially useful as the Clover jars are license-signed for a specific project so you might want to use different jars for different projects. Conditionally instrument test classes too. To instrument test classes set the maven.clover.instrument.teststo true. Make sure that the clover plugin restore other plugin's properties it has modified. Removed public clover:ongoal as it should not have been public. Added unit tests for the plugin and reworked the documentation. Upgraded to Clover 1.2.3. Prevent the plugin from failing if the project on which it is run has no java sources/test sources. Added optional properties to decide what reports to generate. Added a clover:reportgoal which generates all the defined reports. The default is to generate only the HTML report. Allows a new property to be used to specify the sort order of the HTML clover report. Update to use maven.docs.*/maven.gen.docs I register reports only if source, test,... exists. So, corresponding entrys in menu will appear only if reports are registered. Upgrade to Clover 1.2 Make sure that test failures or errors do not stop the generation of the Clover reports. The Clover plugin now depends on version 1.0 of the Clover jar. A special 30-days redistributable clover 1.0 jar (fully functional) has been uploaded to Maven remote repository, making this plugin transparent to use. Creation of this changes page. These changes did not exist at that time. Please refer to CVS for history changes before version 1.1.