maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Gudian (JIRA)" <j...@codehaus.org>
Subject [jira] (SUREFIRE-933) forkMode onceperthread broken after fix for JUnit category filter with empty result
Date Sun, 09 Dec 2012 12:22:13 GMT

    [ https://jira.codehaus.org/browse/SUREFIRE-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315283#comment-315283
] 

Andreas Gudian commented on SUREFIRE-933:
-----------------------------------------

Opened/Updated pull request https://github.com/apache/maven-surefire/pull/13 with a proposed
fix.
                
> forkMode onceperthread broken after fix for JUnit category filter with empty result
> -----------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-933
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-933
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Junit 4.7+ (parallel) support
>    Affects Versions: 2.13
>            Reporter: Andreas Gudian
>
> In forkMode {{onceperthread}} (reusable fork), the {{TestsToRun}} object will always
be a {{LazyTestsToRun}} instance, which throws an excetpion if {{getLocatedClasses()}} is
called. The fix for SUREFIRE-839 changed {{JUnitCoreWrapper}} and {{JUnitCoreProvider}} to
call exactly that method.

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

        

Mime
View raw message