[LANG-1704] ImmutablePair and ImmutableTriple implementation don't match
final in Javadoc
This commit is contained in:
parent
d6b49fda4a
commit
9d85b0a11e
|
@ -49,8 +49,9 @@ The <action> type attribute can be add,update,fix,remove.
|
||||||
<release version="3.13.1" date="202Y-MM-DD" description="New features and bug fixes (Java 8).">
|
<release version="3.13.1" date="202Y-MM-DD" description="New features and bug fixes (Java 8).">
|
||||||
<!-- FIX -->
|
<!-- FIX -->
|
||||||
<action type="fix" dev="ggregory" due-to="remeio">Rename variable names from 'clss' to 'clazz' #1087.</action>
|
<action type="fix" dev="ggregory" due-to="remeio">Rename variable names from 'clss' to 'clazz' #1087.</action>
|
||||||
<action type="fix" dev="ggregory" due-to="remeio">Javadoc: ComparableUtils'c1' to 'comparable1', 'c2' to '
|
<action type="fix" dev="ggregory" due-to="remeio">Javadoc: ComparableUtils'c1' to 'comparable1', 'c2' to '</action>
|
||||||
<action type="fix" dev="ggregory" due-to="Elliotte Rusty Harold">Javadoc: Remove 2.1 specific comment #1091.</action>
|
<action type="fix" dev="ggregory" due-to="Elliotte Rusty Harold">Javadoc: Remove 2.1 specific comment #1091.</action>
|
||||||
|
<action issue="LANG-1704" type="fix" dev="ggregory" due-to="Dan Ziemba, Gilles Sadowski, Alex Herbert, Gary Gregory">ImmutablePair and ImmutableTriple implementation don't match final in Javadoc.</action>
|
||||||
<!-- UPDATE -->
|
<!-- UPDATE -->
|
||||||
<action type="update" dev="ggregory" due-to="Gary Gregory">Bump commons-parent from 58 to 59.</action>
|
<action type="update" dev="ggregory" due-to="Gary Gregory">Bump commons-parent from 58 to 59.</action>
|
||||||
</release>
|
</release>
|
||||||
|
|
|
@ -24,8 +24,7 @@ import java.util.Objects;
|
||||||
*
|
*
|
||||||
* <p>Although the implementation is immutable, there is no restriction on the objects
|
* <p>Although the implementation is immutable, there is no restriction on the objects
|
||||||
* that may be stored. If mutable objects are stored in the pair, then the pair
|
* that may be stored. If mutable objects are stored in the pair, then the pair
|
||||||
* itself effectively becomes mutable. The class is also {@code final}, so a subclass
|
* itself effectively becomes mutable.</p>
|
||||||
* can not add undesirable behavior.</p>
|
|
||||||
*
|
*
|
||||||
* <p>#ThreadSafe# if both paired objects are thread-safe</p>
|
* <p>#ThreadSafe# if both paired objects are thread-safe</p>
|
||||||
*
|
*
|
||||||
|
|
|
@ -23,8 +23,7 @@ import java.util.Objects;
|
||||||
*
|
*
|
||||||
* <p>Although the implementation is immutable, there is no restriction on the objects
|
* <p>Although the implementation is immutable, there is no restriction on the objects
|
||||||
* that may be stored. If mutable objects are stored in the triple, then the triple
|
* that may be stored. If mutable objects are stored in the triple, then the triple
|
||||||
* itself effectively becomes mutable. The class is also {@code final}, so a subclass
|
* itself effectively becomes mutable.</p>
|
||||||
* can not add undesirable behavior.</p>
|
|
||||||
*
|
*
|
||||||
* <p>#ThreadSafe# if all three objects are thread-safe</p>
|
* <p>#ThreadSafe# if all three objects are thread-safe</p>
|
||||||
*
|
*
|
||||||
|
|
Loading…
Reference in New Issue