maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Connolly (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (SUREFIRE-596) Junit test output is broken with junit4-7+
Date Tue, 12 Jan 2010 07:41:55 GMT

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

Stephen Connolly closed SUREFIRE-596.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.5

r898206

> Junit test output is broken with junit4-7+ 
> -------------------------------------------
>
>                 Key: SUREFIRE-596
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-596
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Junit 4.x support
>    Affects Versions: 2.5
>         Environment: junit 4.7
>            Reporter: Kristian Rosenvold
>            Assignee: Stephen Connolly
>             Fix For: 2.5
>
>         Attachments: junit1.diff, junit2.diff, junit2.zip
>
>
> There is a bug in the log output for the junit4.7+ provider, where it just says "Result
null" instead of outputting the 
> proper surefire output. Additionally, the concurrent junit provider should really only
be used
> when the user has requested some concurrent execution model in the configuration.
> Workaround at the moment is one of the following:
> A) Use surefire-2.4.3 until this is fixed
> B) Downgrade to junit 4.6 until this is fixed
> C) ignore the problem. This may be possible, but some CI systems also parse the output
so it may break the build.
> The enclosed patch fixes both problems on svn trunk of surefire, and also includes updated
integration tests.

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

        

Mime
View raw message