This documentation is for Clover 4.0.x. Earlier versions are available here.

Skip to end of metadata
Go to start of metadata

Description

The <clover-merge> task merges several Clover databases into one, to allow for combined reports to be generated. The resultant database can be used with reporting tasks, such as <clover-report> or <clover-log>, using the initstring parameter.

Parameters

Attribute

Description

Required

initstring

The location to write the Clover coverage database resulting from the merge.

Yes.

update

If set to true and there is an existing database at initString, that database will be included in the merge.

No. Defaults to 'false'.

updateSpan

If update is true, this span is used when merging any existing database at initString.

No. Defaults to 0 seconds.

Nested Elements of <clover-merge>

<cloverDb>

Specifies a Clover database to merge.

Parameters

Attribute

Description

Required

initstring

The initString of the database to merge.

Yes.

span

Specifies how far back in time to include coverage recordings from since the last Clover build for this database. See Using Spans.

No; default includes 'all coverage data found'.

<cloverDbSet>

Specifies an Ant FileSet of Clover databases to merge. Apart from those shown below, parameters and sub-elements are the same as for an Ant FileSet.

Parameters

See the Ant FileSet documentation for parameters and sub-elements available on FileSets.

Attribute

Description

Required

refid

Lets you specify a fileset that references a group of Clover database files. This references a fileset defined elsewhere.

No; defaults to none.

span

Specifies how far back in time to include coverage recordings from since the last Clover build for this database. See Using Spans.

No; defaults to '0 seconds'.

Examples

This example produces a merged database containing the measured coverage of project A and project B:

This example produces a merged database containing the measured coverage of all databases found under /home/projects: