[ 
https://issues.apache.org/jira/browse/SUREFIRE-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055294#comment-15055294
 ] 

ASF GitHub Bot commented on SUREFIRE-1194:
------------------------------------------

Github user Tibor17 commented on the pull request:

    https://github.com/apache/maven-surefire/pull/107#issuecomment-164324781
  
    @juherr 
    Do you have this file on your file system?
    `/Users/cbeust/java/testng/target/checkout/lib-supplied/guice-2.0.jar`
    I guess you have it and that's the reason why we have different build 
result.
    Somehow the Maven does not discover the dependencies after unresolved 
system dependency.
    Although you excluded it in IT POM, the Maven failed anyway.
    You tried to exclude it for testng:6.9.9 but that Version has classifier 
which means it was not really excluded.
    The CI Jenkins will fail as well, so we must solve this last issue before 
pushing it to master.
    What about to remove 5.14.9 in your IT?
    Can you please additionally  remove this line `private SurefireLauncher 
verifierStarter;` ?


> 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)

Reply via email to