This is the documentation for Clover 3.3. View this page for the

Unknown macro: {spacejump}

of Clover, or visit the latest Clover documentation.

Skip to end of metadata
Go to start of metadata

Getting the Source Code

The Clover-for-Maven2&3 plug-in source is stored in Mercurial repository on Bitbucket.org. To get a local copy of the source code, a Mercurial client is required.

The following command will checkout the source code of the atlassian/maven-clover2-plugin:

hg clone ssh://hg@bitbucket.org/atlassian/maven-clover2-plugin

(warning) TIP: do not mislead with the atlassian/maven-clover-plugin repository which is a Clover-for-Maven1.

Installing the Plugin

The plugin can then be built, tested and installed via:

mvn clean install

Running Integration Tests

To run the integration tests, use:

mvn clean integration-test -Pintegration-tests

Submitting a Patch

To submit a patch:

  1. Make and test the change in your local subversion work area
  2. Create a JIRA issue in project "Clover" (CLOV), set "Maven Plugin" component.
  3. Ensure any new features/configuration options have been documented in the issue description.
  4. Commit changes and:

or

    • generate a patch by running the following command in your local work area (where XXXX is the id of the JIRA issue created above)

      hg diff > CLOV-XXXX.patch
    • Upload the patch to the JIRA issue you created.

 

 

Binaries

Stable releases can be downloaded from Maven Central or from https://maven.atlassian.com/content/repositories/atlassian-public/com/atlassian/maven/plugins/maven-clover2-plugin

Miscellaneous

(warning) The JIRA issue tracker https://studio.plugins.atlassian.com/browse/CLMVN is deprecated, please raise issues on https://jira.atlassian.com/browse/CLOV

(warning) The SVN respository https://studio.plugins.atlassian.com/svn/CLMVN/trunk is deprecated, use the HG repository from https://bitbucket.org/atlassian/maven-clover2-plugin

 

  • No labels