[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289546#comment-289546 ]
Alexey Yudichev commented on SUREFIRE-799: ------------------------------------------ This is not yet in https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-surefire-plugin/2.12-SNAPSHOT/maven-surefire-plugin-2.12-20120119.191905-28.jar by the looks of it as I'm getting: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.12-SNAPSHOT:test failed: Fork mode perThread is not a legal value Any chance you can deploy a snapshot with this patch in? > Allow test parallelisation when forkMode=always > ----------------------------------------------- > > Key: SUREFIRE-799 > URL: https://jira.codehaus.org/browse/SUREFIRE-799 > Project: Maven Surefire > Issue Type: Improvement > Components: process forking > Affects Versions: 2.10 > Environment: all > Reporter: nkeywal > Assignee: Kristian Rosenvold > Attachments: surefire_799_212_trunk.patch, surefire_799.v2.patch > > > 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. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira