-
Notifications
You must be signed in to change notification settings - Fork 19
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
Generic methods share the same name and signature #222
Comments
It's not just |
Well, it seems that Time to improve on that. |
Should be resolved in release v8.8.74. |
Assuming silence as assent; closing. |
Sorry for the very late reply. Can confirm it is fixed now! Thank you! |
Hi,
when there are two methods just differentiating based on their derived types, they share the same name and signature in the cobertura output.
Here is an example:
This results in a
cobertura.xml
that looks like this:I noticed the issue when I tried to include the output into a Jenkins CI. The coverage plugin threw an Exception, that there is already an item with the key. Just as context, here is the exception thrown by Jenkins:
The text was updated successfully, but these errors were encountered: