[
https://issues.apache.org/jira/browse/SUREFIRE-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17233494#comment-17233494
]
Adam commented on SUREFIRE-1854:
--------------------------------
Hi [~tibordigana],
I analyzed this and need some advice here.
To provide included/excluded engine should I add new parameters to Surefire
plugin or should I reuse configurationParameters for JUnit?
Base on JUnit documentation it looks that including/excluding engine is
separated option, not one of configurationParameters.
[https://junit.org/junit5/docs/current/user-guide/#running-tests-console-launcher-options]
[https://junit.org/junit5/docs/current/user-guide/#running-tests-config-params]
Also this option can be repeated.
So should I create new plugin parameters with multivalue option here?
> 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)