maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Rosenvold (JIRA)" <>
Subject [jira] (SUREFIRE-832) JUnit categories only work when junit47 provider is explicitly set
Date Thu, 09 Feb 2012 16:38:02 GMT


Kristian Rosenvold closed SUREFIRE-832.

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

Fixed with IT in r1242381. The buffering effect is SUREFIRE-817, which is one of the remaining
reasons why this provider is not default for modern JUnit versions.

As for other slowdowns, some kind of evidence like a small sample project would be necessary.
Please file separate issues for distinct problems, do not piggyback further onto this issue.
> JUnit categories only work when junit47 provider is explicitly set
> ------------------------------------------------------------------
>                 Key: SUREFIRE-832
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Junit 4.x support
>            Reporter: Jan Goyvaerts
>            Assignee: Kristian Rosenvold
>             Fix For: 2.13
> If no explicit JUnit 4.7 provider is stipulated, all tests will be run. Regardless of
their @Category annotations. This is contrary to what's stipulated in the documentation; that
the provider will automatically be chosen.
> (why not just use the JUnit dependency of the project btw ? If it's not supporting categories,
you can't use the @Category annotation either).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message