Fix NPE during report aggregation when multiple modules are specified using -pl arg #104
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.
Fixes #103
What changes were proposed in this pull request?
This PR proposes to set
topLevelModule
variable to the current execution root whentopLevelModule
is null.We achieve this by traversing upwards in the maven module hierarchy unless we find a module that returns
true
formodule.isExecutionRoot()
.After this fix, the aggregated report will be available in the current execution root matching the execution behavior of the when
-pl
is not specified.Why are the changes needed?
When report aggregation is run against multiple modules are specified using -pl arg,
topLevelModule
is never set to a non-null value since non of the reactor projects return true formodule.isExecutionRoot()
.How was this patch tested?
Tested the patch manually on the example mentioned in #103