0.33: when two classes have the same name but in different packages, mutation testing output is correct but the source is wrong!

[fge]

The package is this one. I have two classes named DefaultValueStack, one in com.github.parboiled1.grappa.stack and another in org.parboiled.support.

I use the gradle plugin configured as such since the default package is not the group name:

pitest {
    // Since for now it is org.parboiled, we cannot leave the default.
    // By default it is ${project.group}.
    targetClasses = [ "org.parboiled.*", "com.github.parboiled1.*" ];
}

When generating the report, I have the surprise to see that the source of DefaultValueStack displayed for com.github.parboiled1.grappa.stack.DefaultValueStack.java is in fact the one of org.parboiled.support.DefaultValuStack.java...

Surmising at first that this had to do with the order in which the packages were declared in targetClasses, I inverted the order in the above; but it is still org.parboiled.support.DefaultValueStack.java which is displayed.

It therefore appears that the "winner" is always the one which is the greatest wrt canonical string ordering...

[fge]

If that matters, more about my environment:

• gradle 1.12,
• plugin used is (group: "info.solidsoft.gradle.pitest", name: "gradle-pitest-plugin", version: "0.33.0") which uses pitest 0.33,
• TestNG 6.8.7 (although I believe pitest uses its own version, 6.1.1 IIRC),
• tried with Oracle's JDK 6u45, not yet with 7u55 or 8u5 although I would be surprised that it'd change anything.

[nespera]

I've submitted a pull request and confirmed that the report looks correct with this change.

[hcoles]

@fge thanks for the report - surprised that this has been there so long without being spotted. @nespera thanks for the fix, now merged in.