Skip to content

Conversation

gslowikowski
Copy link

Previously only coverage data from dependent modules participated in aggregated report. After this change current module data is added as well.

In some cases this will simplify multi-module project configuration. Dedicated module for aggregated report will not be required. There will be possibility to generate aggregated report for the module depending on all other (if there is such).

Previously only coverage data from dependent modules participated in aggregated report. After this change current module data is added as well.

In some cases this will simplify multi-module project configuration. Dedicated module for aggregated report will not be required. There will be possibility to generate aggregated report for the module depending on all other (if there is such).
@marchof
Copy link
Member

marchof commented May 8, 2018

@gslowikowski This is included unconditionally, right? If the aggregate module contains code this will become part of the report. I assume we make other users unhappy with this change. So probably we need at least a way to make this behavior configurable.

@Godin
Copy link
Member

Godin commented Jan 8, 2019

This was not accepted because #680 (comment) from @marchof was ignored. I'm closing this as duplicate of #812 , which hopefully contains clean description of why this as well as almost identical #430 were not accepted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: maven jacoco-maven-plugin declined: duplicate ❌ This issue or pull request already exists type: enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants