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

2014-09-25 Thread Tibor Digana (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-798. - Resolution: Not A Bug as designed JUnit47 provider could print immediatly the test class name, as

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

2014-09-23 Thread Tibor Digana (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=353046#comment-353046 ] Tibor Digana commented on SUREFIRE-798: --- Nicolas, Can we close this as designed? Another

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

2014-09-23 Thread Nicolas Liochon (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=353060#comment-353060 ] Nicolas Liochon commented on SUREFIRE-798: -- Yeah, it's fine for me. The 2.17 way of

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

2012-01-01 Thread nkeywal (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=287216#comment-287216 ] nkeywal commented on SUREFIRE-798: -- As a side effect as well, note that when a forked process