[
http://jira.codehaus.org/browse/SUREFIRE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122513
]
Dan Fabulich commented on SUREFIRE-449:
---------------------------------------
This is happening because I added @aggregator to surefire-report in order to
fix SUREFIRE-268. I didn't really know what I was doing there, and I'm really
not clear on why this causes the problem, but removing the line seems to help.
I'll need to do more research to make sure this is safe.
> 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
