[jira] Created: (SUREFIRE-797) Parallel junit does not run in parallel when a Suite is used at the top level

Parallel junit does not run in parallel when a Suite is used at the top level - Key: SUREFIRE-797 URL: https://jira.codehaus.org/browse/SUREFIRE-797 Project: Maven Surefire

[jira] Closed: (SUREFIRE-747) Parallel method execution skips Tests

[ https://jira.codehaus.org/browse/SUREFIRE-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-747. --- Resolution: Fixed I'm closing this issue, since I created a separate issue SUREFIRE-797

[jira] Created: (SUREFIRE-798) JUnit47 provider could print immediatly the test class name, as JUnit4, instead of waiting for the test to finish.

JUnit47 provider could print immediatly the test class name, as JUnit4, instead of waiting for the test to finish. -- Key: SUREFIRE-798 URL:

[jira] Created: (MASSEMBLY-581) Allow formats in configuration to override descriptor

Allow formats in configuration to override descriptor - Key: MASSEMBLY-581 URL: https://jira.codehaus.org/browse/MASSEMBLY-581 Project: Maven 2.x Assembly Plugin Issue Type: Bug

[jira] Created: (SUREFIRE-799) Allow test parallelisation when forkMode=always

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

[jira] Created: (SUREFIRE-800) redirectTestOutputToFile is not taken into account with JUnit47 provider

redirectTestOutputToFile is not taken into account with JUnit47 provider Key: SUREFIRE-800 URL: https://jira.codehaus.org/browse/SUREFIRE-800 Project: Maven Surefire

[jira] Commented: (SUREFIRE-800) redirectTestOutputToFile is not taken into account with JUnit47 provider

[ https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=284302#comment-284302 ] nkeywal commented on SUREFIRE-800: -- Seems that I can't edit the title. It should be: not taken

[jira] Commented: (SUREFIRE-760) mvn -Dtest=ClassName#methodName does not work with parallel tests

[ https://jira.codehaus.org/browse/SUREFIRE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=284303#comment-284303 ] nkeywal commented on SUREFIRE-760: -- Thanks a lot for the fix, Kristian! mvn

[jira] Commented: (SUREFIRE-798) JUnit47 provider could print immediatly the test class name, as JUnit4, instead of waiting for the test to finish.

[ https://jira.codehaus.org/browse/SUREFIRE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=284307#comment-284307 ] Kristian Rosenvold commented on SUREFIRE-798: - I assume you're thinking about /when

[jira] Created: (MPIR-236) Crete a new report to show how to include the module in different build systems

Crete a new report to show how to include the module in different build systems --- Key: MPIR-236 URL: https://jira.codehaus.org/browse/MPIR-236 Project: Maven 2.x Project

[jira] Commented: (SUREFIRE-799) Allow test parallelisation when forkMode=always

[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=284308#comment-284308 ] Kristian Rosenvold commented on SUREFIRE-799: - Both parallel forks, balanced parallel

[jira] Commented: (SUREFIRE-798) JUnit47 provider could print immediatly the test class name, as JUnit4, instead of waiting for the test to finish.

[ https://jira.codehaus.org/browse/SUREFIRE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=284310#comment-284310 ] nkeywal commented on SUREFIRE-798: -- Yes, it's when running in serial. I understand that in

[jira] Commented: (MPIR-236) Crete a new report to show how to include the module in different build systems

[ https://jira.codehaus.org/browse/MPIR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=284311#comment-284311 ] Simone Tripodi commented on MPIR-236: - fixed on r1206503 Crete a new report to show how to

[jira] Closed: (SUREFIRE-801) Classloading compatibility break with forkMode=NEVER in 2.9 and 2.10

[ https://jira.codehaus.org/browse/SUREFIRE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-801. --- Resolution: Fixed Fix Version/s: 2.11 Assignee: Kristian Rosenvold

[jira] Updated: (SUREFIRE-751) Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/

[ https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-751: Component/s: process forking Support parallel/fork mode similar to

[jira] Updated: (SUREFIRE-799) Allow test parallelisation when forkMode=always

[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-799: Component/s: (was: Junit 4.7+ (parallel) support) process forking