[ http://issues.apache.org/jira/browse/COLLECTIONS-218?page=comments#action_12422358 ] Stephen Colebourne commented on COLLECTIONS-218: ------------------------------------------------
Its not intuitive, but its not just serialized classes. Our requirement is that other code compiled against collections will continue to work if the new jar is dropped in (without recompilation). Its just a 'feature' of Java that this can't be met. See http://www.eclipse.org/eclipse/development/java-api-evolution.html > CollectionUtils.select() does not return passed in collection > ------------------------------------------------------------- > > Key: COLLECTIONS-218 > URL: http://issues.apache.org/jira/browse/COLLECTIONS-218 > Project: Commons Collections > Issue Type: Improvement > Components: Core > Affects Versions: 3.2 > Reporter: Stephen Kestle > Assigned To: Stephen Colebourne > Attachments: CollectionUtils select return.patch > > > collect has the following methods: > Collection collect(Collection inputCollection, final Transformer transformer) > Collection collect(Collection inputCollection, final Transformer transformer, > final Collection outputCollection) > The first creates an ArrayList(), where the second takes an outputCollection > and, for convenience, returns it. > Select (and selectReject) currently the following methods: > Collection select(Collection inputCollection, Predicate predicate) > void select(Collection inputCollection, Predicate predicate, Collection > outputCollection) > I propose changing the bottom method to return the passed in > outputCollection. It would simplify calling code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
