[
https://jira.codehaus.org/browse/SUREFIRE-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Gier updated SUREFIRE-766:
-------------------------------
Fix Version/s: 2.10
Assignee: Paul Gier
I found that to reproduce the problem, you have to have forkMode set to
"always" or "never". If it's set to "once", the problem goes away. Also, the
problem only occurs when there is a comma in the list of excludes.
> Regression in excludes feature between surefire 2.6 and 2.7.
> ------------------------------------------------------------
>
> Key: SUREFIRE-766
> URL: https://jira.codehaus.org/browse/SUREFIRE-766
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
> Affects Versions: 2.7, 2.7.1, 2.7.2, 2.8, 2.8.1, 2.9
> Reporter: Jonathan Hsieh
> Assignee: Paul Gier
> Fix For: 2.10
>
>
> I have a build that excludes certain JUnit 4 test cases by allowing users to
> specify a -Dtest.exclude.pattern=**/TestA*.java,**/TestB*.java style command
> line argument. This worked for surefire 2.5, 2.6 but fails to work in 2.7,
> 2.7.1, 2.7.2, 2.8, 2.8.1, and 2.9 releases.
> Here's how I pass in the excludes from the command line:
> {code}
> ...
> <plugins> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <forkMode>always</forkMode>
> <includes>
> <include>**/Test*.java</include>
> </includes>
> <excludes>
> <exclude>**/*$*</exclude>
> <exclude>${test.exclude.pattern}</exclude>
> </excludes>
> ...
> {code}
> and
> {code}
> ...
> <properties>
> ...
> <!-- For flaky tests exclusion -->
> <test.exclude />
> <test.exclude.pattern>**/${test.exclude}.java</test.exclude.pattern>
> </properties>
> ...
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
