Vincent Massol Emmanuel Venisse 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.includes and maven.clover.excludes properties to specify what files to include/exclude from the Cloverification. Added new maven.clover.execute.during.report property to control whether or not the clover-report goal builds Cloverify the sources and execute the tests (defaults to true). Deprecated maven.clover.database.dir property and replaced it with a maven.cover.database property that contains not only the database directory but also the name of the database file. clover:off should now reset correctly the maven.build.dest property that clover:on modifies. 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:report goal. Added ability for users to specify their own Clover license file by overriding the new maven.clover.license.path property. Made the following goals public by documenting them: clover:report, clover:on, clover:off, clover:test, clover:test-single. Added new clover:test-single goal 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:get and maven:set. The clover:report goal does not call the tests anymore. It only generates Clover reports. When executing clover:on and clover:off, modify the maven.build.dest property value in the Root context of all plugins so that the value change is available in all Maven plugins. Prevented the clover:on goal 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.