Nick Tan
Nick Tan
hi @krabhishek30 i meant to update your testng jar version of your project (not saying the version of the plugin).
ok, good to know 😄
hi @rajtester what's the version of TestNG Eclipse Plugin you used? could you confirm there is only one testng jar on your classpath?
could you confirm that the plugin you used is latest release `6.9.12.201607091356`, or even you can try with the latest beta http://testng.org/eclipse-beta > I have added some more jars for...
@dassusovan where do you get this 6.8.2 release? i don't even see it on Maven central:  https://search.maven.org/search?q=g:org.testng%20AND%20a:testng&core=gav
@genesisa96 i think it's different issue as of this ticket. but same as what i reported https://github.com/cbeust/testng/issues/2223
Hi as a workaround, you can add guide jar to your project classpath.
@gauravpratap01 if your project dependency is managed with Maven, you can try to add the following `guice` jar to pom.xml: ``` com.google.inject guice 4.1.0 no_aop ```
since Gradle build file is groovy script, which is hard for interpret in term of retrieving the configuration info, rather than Maven, the pom.xml is declarative that easy for machine...
thanks for the tips, that's exactly what I need.