[
https://issues.apache.org/jira/browse/COLLECTIONS-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18114869#comment-18114869
]
Julian Reschke commented on COLLECTIONS-900:
--------------------------------------------
I'll assume that if there's agreement that this is a bug/regression the fix (or
something equivalent) will be applied?
The harder question is: can Oak just wait for a 4.7 release any time soon, or
do we need to workaround the issue in Oak?
> IteratorChain#addIterator() does not work properly with IteratorChain
> parameters
> --------------------------------------------------------------------------------
>
> Key: COLLECTIONS-900
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-900
> Project: Commons Collections
> Issue Type: Bug
> Components: Iterator
> Affects Versions: 4.6.0
> Reporter: Manfred Baedke
> Priority: Major
>
> [https://github.com/apache/commons-collections/pull/628] changed
> IteratorChain#addIterator(final Iterator<? extends E> iterator) so that if
> the parameter iterator is an IteratorChain itself, the method will add it's
> internal iteratorQueue instead of the iterator. Unfortunately,
> IteratorChain#hasNext() modifies this internal queue, so that #addIterator()
> will not work properly anymore. A PR with a test case is linked below.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
