[ 
https://issues.apache.org/jira/browse/LANG-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401110#comment-17401110
 ] 

Lukas Wulff commented on LANG-1668:
-----------------------------------

I worked this out by comparing the two versions on GitHub:

3.11: 
[https://github.com/apache/commons-lang/blob/rel/commons-lang-3.11/src/main/java/org/apache/commons/lang3/reflect/MethodUtils.java]

3.12: 
[https://github.com/apache/commons-lang/blob/rel/commons-lang-3.12.0/src/main/java/org/apache/commons/lang3/reflect/MethodUtils.java]
 

> Unlisted breaking change in behaviour of MethodUtils#getMatchingMethod
> ----------------------------------------------------------------------
>
>                 Key: LANG-1668
>                 URL: https://issues.apache.org/jira/browse/LANG-1668
>             Project: Commons Lang
>          Issue Type: Bug
>          Components: lang.reflect.*
>    Affects Versions: 3.12.0
>            Reporter: Lukas Wulff
>            Priority: Critical
>              Labels: newbie
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to