[
https://issues.apache.org/jira/browse/SUREFIRE-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030867#comment-15030867
]
ASF GitHub Bot commented on SUREFIRE-1194:
------------------------------------------
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-160393834
Your IT has this POM
https://github.com/apache/maven-surefire/blob/master/surefire-integration-tests/src/test/resources/testng-listener-reporter/pom.xml
Did you know it?
There is property testNgVersion and specific surefire config with listeners.
Therefore you should create profile with another surefire config in each.
One profile should be default (activeByDefault) for the old tests.
You can switch on exceptions and debug mode .addGoal( "-e -X" ) in the IT
and then see the log.txt in
`surefire-integration-tests\target\CheckTestNgListenerReporterIT_TestNgListenerReporter\`.
> reporter argument does not work for TestNG
> ------------------------------------------
>
> Key: SUREFIRE-1194
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1194
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
> Affects Versions: 2.19
> Reporter: Testo Nakada
> Assignee: Tibor Digana
> Fix For: 2.19.1
>
>
> TestNG plugin seems to map -reporter command line parameter to reporterslist
> which was removed in TestNG project since 2010
> (a4779524b59330e98ee596c5faa43ae1b33ff844). Therefore, this configuration has
> stopped working since then. The configuration mentioned in
> http://maven.apache.org/surefire/maven-surefire-plugin/examples/testng.html#Using_Custom_Listeners_and_Reporters
> does not work as expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
