olamy opened a new pull request, #3561:
URL: https://github.com/apache/maven-surefire/pull/3561

   Fixes #3560
   
   `<excludes>` now accept method filters, the same way `excludesFile` already 
does:
   
   ```xml
   <exclude>**/SomeTest#testMethod</exclude>
   ```
   
   The class still runs, only the matching methods are skipped.
   
   Only the excludes with a `#` are passed to the method filter. Plain class 
excludes like `**/*$*` behave exactly as before, so they don't start dropping 
JUnit 5 `@Nested` tests inside the fork.
   
   `<includes>` still reject method filters, the error message now just says 
`includes`.
   
   Docs: the `excludes`, `includes`, `test`, `includesFile` and `excludesFile` 
javadoc (surefire and failsafe) and the inclusion/exclusion page now say what 
is supported, and that `test` overrides all four.
   
   Tests: new cases in `AbstractSurefireMojoTest`, a JUnit 5 profile in 
`IncludesExcludesJunit5IT`, and the "excluded classes and methods" case of the 
multiple method patterns ITs now also runs in includes/excludes mode for JUnit 
4 and TestNG.
   
   ---
   
   To make clear that you license your contribution under
   the [Apache License Version 2.0, January 
2004](https://www.apache.org/licenses/LICENSE-2.0)
   check one of the following:
   
   - [ ] I hereby declare this contribution to be licensed under the [Apache 
License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0)
   - [ ] I hereby declare that I have filed an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to