[LANG-1668] Unlisted breaking change in behaviour of MethodUtils#getMatchingMethod

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.12.0
• Fix Version/s: 3.13.0
• Component/s: lang.reflect.*
• Labels: newbie
• Assignee: Unassigned
• Reporter: Lukas Wulff
• Created: 18/Aug/21 14:39
• Updated: 03/Apr/22 18:32
• Resolved: 03/Apr/22 18:32

Description

After upgrading from 3.11 to 3.12 some Unit Tests of mine were failing.
I tracked this back to an undocumented change in lang3:

MethodUtils#getMatchingMethod is behaving differently.

Previously, it returned the closest match when no exact match could be found.

Now, it throws an IllegalStateException when there is no unique result.

It would have saved me some time if this had been noted in the change notes.
Not quite sure where to bring this up or whether this qualifies as a bug, but I hope I'm helping by mentioning it here.