Jan Goyvaerts created MCOBERTURA-159:
----------------------------------------
Summary: Provide support for multi-module project
Key: MCOBERTURA-159
URL: https://jira.codehaus.org/browse/MCOBERTURA-159
Project: Maven 2.x Cobertura Plugin
Issue Type: Improvement
Affects Versions: 2.5.1
Reporter: Jan Goyvaerts
Invoking "clean verify" on the parent of a multi-module project has the effect
that each module is built isolated from the others. As though the targets were
invoked for the modules separately. However, I think in the context of coverage
measurement the semantic should be different.
If the targets were invoked on the parent project, I think the coverage
measurement should be done for all the modules together and result in an
aggregated coverage report. Why else invoke the targets for the parent project
?
Important is that some modules might use each other's classes. Currently it
looks like the shared classes have no coverage at all. While this is not the
case. They're just not located in the same module being tested. (Because they
were not instrumented ?)
An alternative would be to allow the users to specify dependencies to include
in the coverage process. Whether it were a sibling module or not. Which is of
course a recursive process because the included dependency might have cobertura
configured to include other dependencies as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
