Detected method extraction is reported twice

[victorgveloso]

http://lab:4000/refactoring/260/15388201

http://lab:4000/refactoring/260/15388200

The method at
hazelcast/hazelcast@ffa1d33#diff-6c2709c8310d1fad31023d77c616ab752614814b7d811abb8151eebbcb254374R178-R182
has two associated extract method refactoring.
The first is mapped to the invocation at:
hazelcast/hazelcast@ffa1d33#diff-6c2709c8310d1fad31023d77c616ab752614814b7d811abb8151eebbcb254374R172-R172
The second is mapped to the invocation at:
hazelcast/hazelcast@ffa1d33#diff-6c2709c8310d1fad31023d77c616ab752614814b7d811abb8151eebbcb254374R124-R124

[tsantalis]

@victorgveloso
I checked all refactorings and they are correct.
The same method createMessageTask is extracted from multiple different tests.

@pouryafard75
new is not getting matched

[victorgveloso]

@pouryafard75 just explained me that RMiner reports one extracted method refactoring for each method invocation and that is the intended behaviour.

I don't know if that changed recently, but getExtractedOperationInvocations returns an ArrayList hence why I assumed that array could contain multiple values. Instead it always contain a single invocation as the refactoring is split by invocation.

[tsantalis]

Resolved in PR #689