[
https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284308#comment-284308
]
Kristian Rosenvold commented on SUREFIRE-799:
---------------------------------------------
Both parallel forks, balanced parallel forks and reusable forks are part of the
long term plan (which is written on the backside of a napkin I have lying
around here somewhere - if I haven't lost it). Unfortunately I will not be
implementing this until the overall complexity of the surefire forking logic is
reduced to a minimum. This has been an ongoing process since at least version
2.8 and will probably continue for a few more versions after 2.11. If anyone
wants to take a shot at this, go ahead. Just be warned the code is still
changing quite alot in this section.
> Allow test parallelisation when forkMode=always
> -----------------------------------------------
>
> Key: SUREFIRE-799
> URL: https://jira.codehaus.org/browse/SUREFIRE-799
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Junit 4.7+ (parallel) support
> Affects Versions: 2.10
> Environment: all
> Reporter: nkeywal
>
> Surefire already allows:
> - forking
> - parallelization within a JVM
> Mixing both features would mean forking multiple JVM instead of only one.
> It would allow to parallelize tests that need to be executed in a separate
> JVM (i.e.: with forkMode=always). Usually these tests take longer than the
> simple ones. In our case, 40% of the tests are executed in 4 minutes, the
> other 60% need two hours. So it's obviously more interesting to parallelize
> the former, but these ones need to fork.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
