Vincent Massol Emmanuel Venisse Do not execute Clover if there are no tests to run Clover on. This prevents an error happening in the clover:on goal. Allow generating XML and/or Swing reports during the web site generation too. Tests executed after <clover:on are 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.tests to true. Make sure that the clover plugin restore other plugin's properties it has modified. Removed public clover:on goal 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:report goal 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.