[
https://issues.apache.org/jira/browse/SUREFIRE-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SUREFIRE-2100.
---------------------------------------
Fix Version/s: 3.0.0-M8
Assignee: Konrad Windszus
Resolution: Fixed
Fixed in
https://github.com/apache/maven-surefire/commit/c305fc867a8160bf86c1e37713e1258ab6fb68e3.
> Improve behaviour for surefire-report goal with aggregate parameter
> -------------------------------------------------------------------
>
> Key: SUREFIRE-2100
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2100
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Report Plugin
> Affects Versions: 3.0.0-M7
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: 3.0.0-M8
>
>
> The {{aggregate}} parameter affects the default reportDirectories:
> https://github.com/apache/maven-surefire/blob/6f0fb404f89728fb65f37c9db7711fff6af55d5d/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/AbstractSurefireReportMojo.java#L201-L207.
> 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)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
