Open sebastiaanspeck opened 1 year ago
Thank you for this issue @sebastiaanspeck. Is this a problem with sw5-jacoco-reporter, or a problem witch the JaCoCo-plugin in Jenkins?
Though, I do think sw5-jacoco-reporter can do something here. The question is what however... In the same file I would say, ignore all duplicate methods except for the last (with the same name of course).
But what about duplicate methods in different files? I do think Smallworld appends a unique (incrementing) number to each method in the Java Byte Code and from that the last defined (compiled) method can be found.
At least a warning can be shown during the conversion.
The issue raises as soon as you use the JaCoCo-plugin in Jenkins, but it originates from the sw5-jacoco-reporter (actually the Magik-code ofcourse).
I think a warning during conversion seems enough for me I think, you need to resolve duplicated methods in the Magik-code.
I will take a look how the XML will look when having the duplicated method in a different file and will append it here.
When having the next exemplar in Magik:
Creating the next jacoco.xml:
The double method definition with name
simple_exemplar.duplicated_method()
causes the next error when pushing this to the JaCoCo-plugin in Jenkins: