[
https://issues.apache.org/jira/browse/SUREFIRE-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17234408#comment-17234408
]
Tibor Digana commented on SUREFIRE-1854:
----------------------------------------
Hi [~adam11grafik]
I also expected the methods {{configurationParameter()}} and
{{configurationParameters()}} to accept the option {{--include-engine}}.
We should confirm (by a test) that this is not the way, and then we should
create new parameters to Surefire plugin.
We already use the {{configurationParameters()}} in the [JUnit5
provider|https://github.com/apache/maven-surefire/blob/master/surefire-providers/surefire-junit-platform/src/main/java/org/apache/maven/surefire/junitplatform/JUnitPlatformProvider.java#L197]
but I am sceptic that this would help us.
T
> Support include/exclude junit test engine
> -----------------------------------------
>
> Key: SUREFIRE-1854
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1854
> Project: Maven Surefire
> Issue Type: New Feature
> Components: JUnit 5.x support, Maven Surefire Plugin
> Affects Versions: 2.22.2
> Reporter: Adam
> Priority: Major
>
> It could be very important for my project to support include/exclude junit
> test engine by Maven Surefire Plugin.
> Junit Console Launcher have existing support for this:
> [https://junit.org/junit5/docs/current/user-guide/#running-tests-console-launcher-options]
> Similar solution exists for Gradle:
> https://junit.org/junit5/docs/current/user-guide/#running-tests-build-gradle
--
This message was sent by Atlassian Jira
(v8.3.4#803005)