[
https://issues.apache.org/jira/browse/LANG-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748798#comment-17748798
]
Alex Herbert commented on LANG-1704:
------------------------------------
Note: Now 3.13.0 is released changing back to final for the class would be a
binary incompatible change. A reversion would require an exclusion on the
compatibility check.
Any class extending this would have to reimplement the storage of the pair to
be mutable. But it is still possible, and not in keeping with the supposed
intention of the class.
> ImmutablePair and ImmutableTriple not actually final as documented
> ------------------------------------------------------------------
>
> Key: LANG-1704
> URL: https://issues.apache.org/jira/browse/LANG-1704
> Project: Commons Lang
> Issue Type: Bug
> Components: lang.tuple.*
> Affects Versions: 3.13.0
> Reporter: Dan Ziemba
> Priority: Minor
>
> As of commons-lang3 3.13.0, the ImmutablePair and ImmutableTriple classes are
> no longer final, even though their javadocs claim that they are. This is a
> problem because you can now subclass those and, for example, make an
> effectively mutable object that could be passed to a method with a parameter
> of type ImmutablePair.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
