Adding an additional report-aggregate-module mojo which aggregate using module instead of dependency #448
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@hcoles
@rchargel
I've slightly modified the new "aggregate-report" mojo class in order to do the aggregation of the report for all the submodule of a project, instead of adding an aggregate project with dependencies.
The configuration of the aggregation will be so much easier and cleaner this way.
(you can configure everything in the parent project, and you don't have to create a project dedicated to the aggregatation.)
Unfortunately, This method is not compatible with the old report-aggegate mojo, so I had to create a new mojo.
To use-it:
in the pom parent
then the command-libe
mvn pitest:report-aggregate-module