[jira] (SUREFIRE-1126) Discrepancy between test exclusion docs and plugin behavior

["Tibor Digana (JIRA)" <ji...@codehaus.org>]

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

Tibor Digana commented on SUREFIRE-1126:
----------------------------------------

Since of 2.19 the exclamation mark (!) is applicable to regex and non-regex format.

Additionally available Multiple Classes and Methods, regex, non-regex support for JUnit4, JUnit47+, TestNG providers.
https://github.com/apache/maven-surefire/pull/83

> Discrepancy between test exclusion docs and plugin behavior
> -----------------------------------------------------------
>
>                 Key: SUREFIRE-1126
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-1126
>             Project: Maven Surefire
>          Issue Type: Bug
>    Affects Versions: 2.18
>            Reporter: Dima Spivak
>            Assignee: Tibor Digana
>             Fix For: 2.19
>
>
> According to [Surefire documentation|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#test], tests can be excluded on the command line by prefixing with an exclamation mark. Is this expected behavior that's currently broken, or did someone jump the gun with the docs?



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)