[
https://issues.apache.org/jira/browse/SUREFIRE-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054846#comment-15054846
]
ASF GitHub Bot commented on SUREFIRE-1194:
------------------------------------------
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-164236954
I was about to push your commit and start the release Vote.
Please run the ITs. I found a problem in IT
Tests in error:
testNgListenerReporter[4: TestNG
5.14.4](org.apache.maven.surefire.its.CheckTestNgListenerReporterIT)
`java.lang.NoClassDefFoundError: com/beust/jcommander/ParameterException`
The exception class is really missing in JAR and `TestNG` and
`RemoteTestNG` class are referencing the exception.
Do not hesitate to express the Warning and message in
`MojoExecutionException` in `AbstractSurefireMojo` in detail, e.g. testng pom
contains system scope artifact `org.testng:guice:2.0`. Other reason like you
already mentioned in `CheckTestNgListenerReporterIT` comments.
According to the comment in your IT Version 5.14.5 is wrong? Treatment was
to exclude guice artifact?
> 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)
