[
https://issues.apache.org/jira/browse/SUREFIRE-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029272#comment-15029272
]
ASF GitHub Bot commented on SUREFIRE-1194:
------------------------------------------
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-159998029
You can override the TestNG version by `resetInitialGoals( version )`
method and you can see the usage of the method in `CheckTestNgVersionsIT`. The
version is passed to the pom.xml in the IT via system property "testNgVersion".
You can see it in folder "testNgVersion" because `CheckTestNgVersionsIT`
extracts test project which appears in `testng-simple`. See
https://github.com/apache/maven-surefire/tree/master/surefire-integration-tests/src/test/resources/testng-simple
and see `<version>${testNgVersion}</version>` which is the system property
key.
See `unpack( "testng-simple" )`.
I think you can extend the test `CheckTestNgListenerReporterIT` with new
test method using TestNG 6.0. See the IT project extracted by `unpack(
"testng-listener-reporter" )`.
> 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)
