[
https://issues.apache.org/jira/browse/SUREFIRE-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879217#comment-17879217
]
Slawomir Jaranowski commented on SUREFIRE-1737:
-----------------------------------------------
similar is for standard {{{}statelessTestsetReporter{}}}, I need use a
deprecate parameter: {{disableXmlReport}}
> Disabling the JUnit5Xml30StatelessReporter has no effect
> ---------------------------------------------------------
>
> Key: SUREFIRE-1737
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1737
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 3.0.0-M4
> Reporter: Dietrich Schulten
> Priority: Major
>
> I have the following configuration for JUnit 5 display names:
> {code:java}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>3.0.0-M4</version>
> <configuration>
> <statelessTestsetReporter
> implementation="org.apache.maven.plugin.surefire.extensions.junit5.JUnit5Xml30StatelessReporter">
> <disable>true</disable>
> <usePhrasedFileName>true</usePhrasedFileName>
> <usePhrasedTestSuiteClassName>true</usePhrasedTestSuiteClassName>
> <usePhrasedTestCaseClassName>true</usePhrasedTestCaseClassName>
> <usePhrasedTestCaseMethodName>true</usePhrasedTestCaseMethodName>
> </statelessTestsetReporter>
> </configuration>
> </plugin>{code}
> Based on the disable flag, the {{JUnit5Xml30StatelessReporter}} should be
> {{disabled}}, but it evaluates display names according to the
> {{usePhrasedXXX}} flags.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
