Changes in Clover-for-Ant 3.3.0

March 31, 2014

This is a feature release with dedicated support for the Spock framework and JUnit4 Parameterized Tests.

See Clover 3.3 Release Notes for more details.

Implemented features and fixes

See also change log for Clover-for-Maven2&3, Clover-for-Eclipse, Clover-for-IDEA, Clover-for-Grails.

Known major bugs

Changes in Clover-for-Ant 3.2.2

February 7, 2014

This release contains fixes for Java 8 language support and solves compatibility issues with the latest Grails 2.3.

Implemented features and fixes

See also change log for Clover-for-Maven2&3, Clover-for-Eclipse, Clover-for-IDEA, Clover-for-Grails.

Known major bugs

Changes in Clover-for-Ant 3.2.1

January 10, 2014

This is a bug fix release which fixes compatibility issues with IDEA 13 and Eclipse.

Implemented features and fixes

See also change log for Clover-for-Maven2&3, Clover-for-Eclipse, Clover-for-IDEA, Clover-for-Grails.

Known major bugs

Changes in Clover-for-Ant 3.2.0

October 21, 2013

This is a major release with support for Java8. See Clover 3.2 Release Notes.

Implemented features and fixes

See also change log for Clover-for-Maven2&3, Clover-for-Eclipse, Clover-for-IDEA, Clover-for-Grails.

Known bugs

Changes in Clover-for-Ant 3.1.12.1

July 22, 2013

This bug fix release contains a fix in the com.cenqua.clover:clover core artifact for Clover-for-Bamboo.

CLOV-1326 - Getting issue details... STATUS

Changes in Clover-for-Ant 3.1.12

June 27, 2013

This is a bug fix release which addresses issues found in 3.1.11 and earlier versions of Clover-for-Ant.

Improvements

1) The main improvement implemented in this release is related with an IDEA12 "external build" feature - see Clover-for-IDEA change log.

2) The <clover-report> task supports the <columns> option for PDF report. Thanks to this you can customize list of metrics to be displayed in a PDF report.

3) We have prepared a new Clover in 10 minutes tutorial for Ant.

JIRA issue list

See also change log for Clover-for-Maven2&3, Clover-for-Eclipse, Clover-for-IDEA, Clover-for-Grails.

Changes in Clover-for-Ant 3.1.11

March 25, 2013

This is a bug fix release which addresses issues found in 3.1.10 and earlier versions of Clover-for-Ant.

Migration notes

1) Class names of Clover's Ant types have been changed from "com.cenqua.*" to "com.atlassian.*". As cloverlib.xml and cloverjunitlib.xml files from clover.jar have been updated accordingly, migration shall be transparent, unless your build scripts refers to a given class name directly. New class names are as follows:

• clover-optimized-selector = com.atlassian.clover.types.CloverOptimizedTestSelector
• clover-ant170-check = com.atlassian.clover.types.CloverAnt170CheckType
• clover-optimized-testset = com.atlassian.clover.types.CloverOptimizedTestSet
• always-run = com.atlassian.clover.types.CloverAlwaysRunTestSet

2) Clover property clover.offrails.coverage is no longer used. Instead of this, define <profile coverageRecorder="GROWABLE"> - see below.

3) The Clover-for-Maven1, Clover-for-Maven2&3 have been migrated from studio.plugins.atlassian.com to bitbucket.org (CLOV-1197). Also Clover-for-Grails code is hosted on Bitbucket.

Improvements

1) It is possible to disable Clover for instrumented code at runtime. If you define:

-Dclover.enable=false

property, then coverage data will not be recorded. This option can be useful in case you'd like to disable coverage recording for some subset of tests, without building code twice (i.e. with and without Clover instrumentation).

2) It is possible to define multiple runtime profiles for Clover and select one of them at runtime by a following property:

-Dclover.profile=<profile name>

Thanks to this you can run instrumented application in several configurations, without need to rebuild the code. Currently supported options are: <distributedCoverage> tag and coverageRecorder="type" attribute. In future more options will be added. Read <profiles> for more details.

3) It is possible to choose among three Clover's coverage recorder types:

• FIXED - standard recorder with a fixed-size array for hit counts, which requires a presence of clover.db at runtime
• GROWABLE - recorder with a dynamically resizeable array for hit counts, does not need clover.db at runtime
• SHARED - recorder designed for large Grails applications

More details: Coverage Recorders.

4) The com.cenqua.clover.SnapshotPrinter tool is able to print content of the test optimization snapshot in the JSON format. 

JIRA issue list

See also change log for Clover-for-Maven2&3, Clover-for-Eclipse, Clover-for-IDEA, Clover-for-Grails.

Changes in Clover-for-Ant 3.1.10

January 8, 2013

This is a bug fix release which addresses issues found in 3.1.8 and earlier versions of Clover-for-Ant.

Improvements

1) Two new metrics have been implemented for method context filter:

• maxAggregatedStatements
• maxAggregatedComplexity

These two metrics calculate method statements/complexity including the code of all anonymous inline classes declared inside the method. Thanks to this it is possible to distinguish between trivial single-statement methods like:

int getNumber() { 
   return this.number;
}

and single-statement methods which actually return more complex data, like:

ActionListener getListener() {
   return new ActionListener() {
       public void actionPerformed(ActionEvent e) {
           System.out.println("statement #1");
           System.out.println("statement #2");
           System.out.println("statement #3");
       }
   }; 
}

In the code sample above, the getListener() method has only one statement: "return new ActionListener()". If you would use a method context filter with maxStatements attribute, like:

<methodContext name="trivial" regexp=".*" maxStatements="1">

then the whole method would be filtered-out (because it contains one "return" statement). If you would use new maxAggregatedStatements, for instance:

<methodContext name="trivial" regexp=".*" maxAggregatedStatements="1">

then the getListener() method would not be filtered out (because it contains 4 statements in total - 1 "return" statement from the method itself and 3 "System.out.println()" statements from anonymous class).

2) The <testsources> tag from <clover-setup> task is now passed to <groovyc> Ant task. Thanks to this you can define custom test detection rules for Groovy code. See clover-setup task for more details.

JIRA issue list

See also change log for Clover-for-Maven, Clover-for-Eclipse, Clover-for-IDEA.

Changes in Clover-for-Ant 3.1.8

13 November, 2012

This is a bug fix release which addresses issues found in 3.1.7 and earlier versions of Clover-for-Ant.

Improvements

1) Fixed bug which was causing java.lang.IncompatibleClassChangeError in case when Groovy 2.x compiler was called from Ant.

2) Clover can now intercept the GrailsTestCompiler from Grails 2.x (which is being used for compilation of unit tests).

3) It is possible to upgrade third party libraries bundled in Clover using the new utility.

4) It is possible to define location/name of the dynamically created grover*.jar artifact (used for compilation of Groovy code, by default in java.io.tmpdir) or to disable its creation at all.

5) Fixed bug causing that only a subset of coverage files was used for calculation of coverage in case when application was executed in IBM JRE.

See also change log for Clover-for-Maven, Clover-for-Eclipse, Clover-for-IDEA.

JIRA issue list

Changes in Clover-for-Ant 3.1.7

31 August, 2012

This is a bug fix release which addresses issues found in 3.1.6 and earlier versions of Clover-for-Ant.

Improvements

Improved behaviour of <clover-report includeFailedCoverage="false"/>. When includeFailedCoverage parameter is set to false, it will not only ignore failed coverage when calculating Total Coverage percentage, but also reflect it in syntax highlighter:

• source lines will be coloured in red and hit count will show 0 for failed tests,
• but at the same time the yellow test marker line is still visible and you can click it to see test contribution pop-up

(Please note that in case of partially covered source line, the whole line is marked red; it's a limitation of our Velocity template).

Documentation

We're happy to announce that we've extended manual:

• Working+with+Distributed+Applications

and prepared two completely new manuals:

• Using+Clover+in+various+environment+configurations

• Using+Clover+for+web+applications

JIRA issue list

Changes in Clover-for-Ant 3.1.6

19 June, 2012

This is a bug fix release which addresses issues found in 3.1.5 and earlier versions of Clover-for-Ant.

Changes in Clover-for-Ant 3.1.5

25 April, 2012

Clover 3.1.5 is a bug fix release addressing issues found in Clover 3.1.4.

Changes in Clover-for-Ant 3.1.4

27 February, 2012

Clover 3.1.4 is a bug fix release addressing issues found in Clover 3.1.3.

Changes in Clover-for-Ant 3.1.3

17 January, 2012

Clover 3.1.3 is a bug fix release addressing issues found in Clover 3.1.2.

Changes in Clover-for-Ant 3.1.2

7 November, 2011

Clover 3.1.2 is a bug fix release addressing issues found in Clover 3.1.0. Clover 3.1.0 introduced support for Java 1.7 language features.

Changes in Clover-for-Ant 3.1.0

2 June, 2011

Clover 3.1.0 is a release that introduces support for Java 1.7 language features and fixes various bugs.