Konrad Windszus opened SUREFIRE-2100 and commented
The aggregate parameter affects the default reportDirectories:
|
if ( this.reportsDirectories == null ) |
|
{ |
|
for ( MavenProject mavenProject : getProjectsWithoutRoot() ) |
|
{ |
|
resolvedReportsDirectories.add( getSurefireReportsDirectory( mavenProject ) ); |
|
} |
|
} |
.
This default behaviour only makes sense though for a Maven project containing multiple modules. For a single Maven project this default behaviour leads to the fact that always an empty report is being generated as the root project is always(!) skipped.
Although one could argue that aggregate should only ever be set for multimodule projects, one can easily fix the logic here to also work for a singlemodule project. Also the javadoc of this argument does not state any limitations on when to use it (https://maven.apache.org/surefire/maven-surefire-report-plugin/failsafe-report-only-mojo.html#aggregate)
Affects: 3.0.0-M7
Remote Links:
Konrad Windszus opened SUREFIRE-2100 and commented
The
aggregateparameter affects the default reportDirectories:maven-surefire/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/AbstractSurefireReportMojo.java
Lines 201 to 207 in 6f0fb40
This default behaviour only makes sense though for a Maven project containing multiple modules. For a single Maven project this default behaviour leads to the fact that always an empty report is being generated as the root project is always(!) skipped.
Although one could argue that
aggregateshould only ever be set for multimodule projects, one can easily fix the logic here to also work for a singlemodule project. Also the javadoc of this argument does not state any limitations on when to use it (https://maven.apache.org/surefire/maven-surefire-report-plugin/failsafe-report-only-mojo.html#aggregate)Affects: 3.0.0-M7
Remote Links: