[
https://issues.apache.org/jira/browse/COLLECTIONS-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838990#comment-17838990
]
Alex Herbert commented on COLLECTIONS-842:
------------------------------------------
I meant that the API implemented in AbstractLinkedList will be removed as it is
deprecated. Thus Collections 5 would have the replacement, e.g. BaseLinkedList.
This could be renamed as AbstractLinkedList. But the API will be compatible
with JDK 21.
Any code migration to Collections 5 will have to change package name and
recompile the source. So we can recycle the AbstractLinkedList name from
whatever the compatible version is named in Collections 4. This means the name
choice for the replacement is not fixed for the long term, but would exist only
in Collections 4. So the pragmatic choice suggested is self-documenting.
Would you like to raise a PR to implement the proposed "Must Haves" changes?
> AbstractLinkedList incompatible with JDK 21's java.util.List
> ------------------------------------------------------------
>
> Key: COLLECTIONS-842
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-842
> Project: Commons Collections
> Issue Type: Bug
> Components: List
> Reporter: Julian Reschke
> Priority: Major
>
> ...it returns "boolean" in commons-collections4, but is void in JDK 21 (see
> https://download.java.net/java/early_access/jdk21/docs/api/java.base/java/util/List.html#addLast(E))
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
