You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org> on 2011/05/08 22:07:22 UTC

[jira] Closed: (SUREFIRE-703) surefire-junit47doesn't work with redirectTestOutputToFile option

     [ http://jira.codehaus.org/browse/SUREFIRE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Rosenvold closed SUREFIRE-703.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.8.2
         Assignee: Kristian Rosenvold

Fixed in r1097246, integration test for this specific issue added in t1100803. Thanks for the testcase!

> surefire-junit47doesn't work with redirectTestOutputToFile option
> -----------------------------------------------------------------
>
>                 Key: SUREFIRE-703
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-703
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Junit 4.7+ (parallel) support
>    Affects Versions: 2.7.2
>            Reporter: Will May
>            Assignee: Kristian Rosenvold
>             Fix For: 2.8.2
>
>         Attachments: surefire-junit47-it.patch
>
>
> If you have the redirectTestOutputToFile option set and use the surefire-junit47 provider (through using the parallel test option or through forcing it), then the output file will just contain a single newline and so the console logging will be completely lost.
> Attached is an integration test showing this issue which was based off of the fork-consoleOutput integration test.

-- 
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