OpenClover 4.2.0 Release Notes

OpenClover 4.2.0 is available

It is based on the open-sourced version of Atlassian Clover® 4.1.2. Scope:
We released: Clover Runtime, Core, Ant, Eclipse, IDEA, Maven, Grails, AspectJ, Hudson and Jenkins (Gradle plugin is still pending).

Note: the Hudson wiki is down, but the artifact is available.

Features

No license key required

OpenClover requires no license key, in some places you may see a "Clover free edition" message. You no longer need any external license key to run it. In case you still pass the license key issued by Atlassian in your builds (e.g. via -Dclover.license.path JVM property), it will be ignored and the built-in one will be used.

This license key gives you full set of features - there is no "Clover Desktop" or "Clover Server" license anymore. In case you were using Desktop license previously, now you can enjoy having HTML / XML / PDF reports generated directly from your Eclipse or IntelliJ IDEA - try the HTML one - it's awesome!

Upgrading from Clover 4.1.x

License key

As OpenClover comes with the built-in license key, you no longer have to pass any license key for instrumentation or report generation. Thus, you can remove any -Dclover.license or -Dclover.license.path JVM properties as well as remove <license> or <licenseLocation> properties from pom.xml.

Clover for Ant

Simply download new Clover-for-Ant zip file and use the clover.jar from it.

Clover for Eclipse

In case you have Atlassian Clover® installed - disable Clover on all your projects in the workspace and next uninstall the plugin. Next, install the OpenClover version and enable Clover on your projects again.

Clover for IDEA

Uninstall Atlassian Clover® for IDEA. Install OpenClover plugin.

Clover Maven Plugin

Clover Core artifact has been renamed from 'com.atlassian.clover:clover' to 'org.openclover:clover'. Clover Maven Plugin artifact has been renamed from 'com.atlassian.maven.plugins:clover-maven-plugin' to 'org.openclover:clover-maven-plugin'. Update these references in pom.xml files.

The most probably you have also the 'com.atlassian.maven.plugins' group defined in ~/.m2/settings.xml file. This allows to use a short name to run Clover from command line. Replace it with:
<pluginGroups>
    <pluginGroup>org.openclover</pluginGroup>
</pluginGroups>

Grails Clover Plugin

It's still named 'org.grails.plugins:clover', so simply upgrade to version 4.2.0 to start using OpenClover

Please note that Grails Clover Plugin does not support Grails 3 yet.

Bamboo Clover Plugin

In case you use automatic Clover integration in Bamboo, then you have to switch it to manual one, as Bamboo is using Atlassian Clover® instead of OpenClover. In case of a Maven task, the manual integration should define goals similar to the following:
clean org.openclover:clover-maven-plugin:setup verify org.openclover:clover-maven-plugin:aggregate org.openclover:clover-maven-plugin:clover

Jenkins Clover Plugin

Name of the plugin did not change, so simply upgrade to the latest 4.8.0 version to use OpenClover. In case you use Maven integration, you may need to change the goals called - see example for Bamboo.

Hudson Clover Plugin

Name of the plugin did not change, so simply upgrade to the latest 4.7.0 version to use OpenClover. In case you use Maven integration, you may need to change the goals called - see example for Bamboo.

Gradle Clover Plugin

We have not released the OpenClover version of the Gradle plugin yet. You can find its source code here: https://bitbucket.org/openclover/gradle-clover-plugin