You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Martin Ackermann (JIRA)" <ji...@codehaus.org> on 2011/01/22 10:17:58 UTC

[jira] Updated: (SUREFIRE-688) Aggregate report is empty for multi-module project

     [ http://jira.codehaus.org/browse/SUREFIRE-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ackermann updated SUREFIRE-688:
--------------------------------------

    Attachment: trial-maven.zip

> Aggregate report is empty for multi-module project
> --------------------------------------------------
>
>                 Key: SUREFIRE-688
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-688
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Report Plugin
>    Affects Versions: 2.7.1
>         Environment: Maven 3.0.1, Site 3.0-beta-3, Windows XP SP3
>            Reporter: Martin Ackermann
>            Priority: Minor
>         Attachments: trial-maven.zip
>
>
> The parent project has a site configuration with an aggregated surefire report and inherited set to false. The child module has one test. 
> Problem: "mvn clean; mvn site-deploy" creates a surefire report with zero tests. With 2.7.2-SNAPSHOT as of today the problem is the same.
> Why does the surefire report plugin not immediately descend to the child modules, compile and test them while executing the aggregate report for the parent module?
> The problem seems to be that the aggregate surefire report for the parent is generated but the surefire plugin doesn't run the tests for the child modules before. So the aggregate surefire report doesn't find any surefire test results for the child modules.
> If I run "mvn clean test; mvn site-deploy", the resulting aggregate surefire report is correct. The reason is probably that the site-deploy collects the surefire results for the child modules from the previous run.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira