[
http://jira.codehaus.org/browse/MCOBERTURA-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257793#action_257793
]
T G commented on MCOBERTURA-65:
-------------------------------
I also like the idea of this plugin, and think it works pretty well. I have
only two complaints:
1. I agree that 'agregate' should be renamed to 'aggregate' everywhere to be
spelled correctly
2. (This is infinitely more important) When I use the plugin to aggregate the
reports, compexity becomes 0 for every single thing, when they are *not* 0 in
the un-aggregated files.
I need complexity to be shown for each of the packages, but I am having a hard
time finding where complexity would have gotten dropped from the report, in
Anthonin's code. Any ideas how to fix this to show complexity again? Thanks.
> Cobertura should aggregate results of multi-module builds
> ---------------------------------------------------------
>
> Key: MCOBERTURA-65
> URL: http://jira.codehaus.org/browse/MCOBERTURA-65
> Project: Maven 2.x Cobertura Plugin
> Issue Type: Improvement
> Environment: Windows
> Reporter: David Hoffer
> Attachments: cobertura_aggregate.diff
>
>
> When I run a cobertura report on parent pom project that has child modules I
> only get reports generated for each module, I also want to see a combined
> report in the parent.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
