[
http://jira.codehaus.org/browse/MCOBERTURA-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258022#action_258022
]
T G commented on MCOBERTURA-65:
-------------------------------
@ James Ahlborn- I used your patch, and it works well, and is more consolidated
than the other option (and spelled correctly).
However, I have the same problem here that I have with his other patch. When I
run the <aggregate>true</aggregate>, the aggregated report for the parent
projects are complete except *missing* complexities, but the children each have
complete reports, *with* complexities.
What do you think could be happening? Is the .ser file getting cut when it is
aggregated? Please let me know if you have any ideas. Feel free to email my
personal email with suggestions.
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
