[
http://jira.codehaus.org/browse/MCLOVER-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Allen updated MCLOVER-80:
------------------------------
Attachment: MCLOVER-80.diff
After discussion it appears that some people would like aggregate to include
all the projects within the reactor, regardless of their inheritance
relationship to the parent project (i.e. the existing behaviour) and others
would like the inheritance hierarchy to be honoured in aggregation.
This latest patch supports both these configurations with the addition of a new
configuration option 'aggregateOnlyChildren'.
> aggregate is not respecting the true module hierarchy and creates merged
> databases containing non-sibling data
> --------------------------------------------------------------------------------------------------------------
>
> Key: MCLOVER-80
> URL: http://jira.codehaus.org/browse/MCLOVER-80
> Project: Maven 2.x Clover Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: John Allen
> Attachments: MCLOVER-80.diff, MCLOVER-80.diff, MCLOVER-80.diff,
> MCLOVER-80.diff
>
>
> The reactor contains a very deep multi-project multi-module structure. We
> would expect the aggregation to only go up the family tree and not pollute
> across the ancestors.
> A-->B-->C-->D
> A-->B-->E
> A-->Q-->P-->R
> A-->Q-->P-->S
> We would expect A to contain all the merged data but not to find that in P we
> have data from C and D.
--
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
