Sonar does not produce aggregate code coverage results when using Clover in multi-module Maven projects

This issue is related to Sonar 613: http://jira.codehaus.org/browse/SONAR-613?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel#issue-tabs

Clover analyses code coverage for Maven module projects for tests that run in the test and integration-test phase of the Maven build lifecycle.

This works fine when Sonar is switched to Clover.

However, Clover also aggregates tests from across modules in multi-module Maven projects. So, if one module is called acceptance-tests and is run that results in code coverage in a service module, the code coverage for the service module will be calculated based on not only the tests that are part of the service module, but the acceptance-tests execution too. This is achieved by using the clover2:aggregate command from the command line, as documented here:

http://confluence.atlassian.com/display/CLOVER/Clover-for-Maven+2+Installation+Guide

Sonar should not remove the ability to use this function so the true code coverage for multi-module Maven projects is displayed on the dashboard.