-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting Ambiguous method overloading for method org.testng.Assert.assertEquals() in Groovy version 3.0.19 #3034
Comments
@PrakratiAgarwal123 - can you please share a sample project ( along with the dependencies) that can be used to reproduce this issue? |
Other versions are - <groovy-all.version>3.0.19</groovy-all.version>
<gmavenplus-plugin.version>2.0.0</gmavenplus-plugin.version>
<maven-assembly-plugin.version>3.6.0</maven-assembly-plugin.version>
<maven-resources-plugin.version>3.3.1</maven-resources-plugin.version>
<maven-dependency-plugin.version>3.6.0</maven-dependency-plugin.version>
<maven-compiler-plugin.version>3.11.0</maven-compiler-plugin.version>
<maven-jar-plugin.version>3.2.0</maven-jar-plugin.version>
<maven-surefire-plugin.version>3.1.2</maven-surefire-plugin.version>
<build-helper-maven-plugin.version>3.3.0</build-helper-maven-plugin.version>
<testng.version>7.9.0</testng.version> |
@PrakratiAgarwal123 - Please create and share a sample project using which I can reproduce the problem easily. |
Its the similar issue like this link and I am using testng version 7.8.0 |
@PrakratiAgarwal123 - Your earlier comment said you are using I would be curious to know as to what is the issue with sharing a simple maven/gradle project that we can use to reproduce the problem? I |
Ambiguous method overloading for method org.testng.Assert#assertEquals. Cannot resolve which method to invoke for [class java.lang.Integer, class java.lang.Integer] due to overlapping prototypes between: [int, class java.lang.Integer] [class java.lang.Integer, int]
Code is -
Same code was working in groovy version 2.5.7
The text was updated successfully, but these errors were encountered: