[jira] Updated: (SUREFIRE-449) In multi-module projects, all tests are run for each module in the module tree

["Dan Fabulich (JIRA)" <ji...@codehaus.org>]

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

Dan Fabulich updated SUREFIRE-449:
----------------------------------

    Fix Version/s: 2.4.2

Thanks for filing this bug; I noticed it too but thought it was just SUREFIRE-257 (which is really a bug in core).  But I'm able to reproduce your findings that this wasn't a problem in 2.3, so I'll happily take a crack at it.

> In multi-module projects, all tests are run for each module in the module tree
> ------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-449
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-449
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: report plugin
>    Affects Versions: 2.4
>         Environment: Maven 2.0.8, Linux
>            Reporter: Stefan Seidel
>            Priority: Blocker
>             Fix For: 2.4.2
>
>         Attachments: mvnexec.zip
>
>
> In a multi-module project, since version 2.4, all tests of all modules are run once for each module. This is *very* bad with many modules & many tests. Attached is a sample project which contains a parent module and two child modules. Each of the child modules contains one JUnit test. mvn clean site runs each test three times (once for the parent and once for each of the two submodules). When changing the surefire-report-plugin to version 2.3, each test is run only once, as it is supposed to

-- 
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