[ https://issues.apache.org/jira/browse/COLLECTIONS-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999876#comment-13999876 ]
Joerg Schaible commented on COLLECTIONS-527: -------------------------------------------- Ignat, I understand the problem, but it does not make sense. If we modify this method in the interface, commons-collections 3.x is no longer compatible with any previous 3.x release and can break *any* jar that depends on cc-3.x (at least on MultiMap) unles it is *modified* itself and rebuilt. Sorry, this situation would be even worse. > Please create a version commons-collections 3.x for jdk 8 compatibility > ----------------------------------------------------------------------- > > Key: COLLECTIONS-527 > URL: https://issues.apache.org/jira/browse/COLLECTIONS-527 > Project: Commons Collections > Issue Type: Bug > Reporter: Ignat Alexeyenko > Priority: Blocker > Labels: java8, jdk8 > Attachments: COLLECTIONS_3_2_BRANCH_COLLECTIONS_527.patch > > > Could you make a 3.x or 3.2.x release compatible with JDK8 ? > {code} > org.apache.commons.collections.MultiMap { > public Object remove(Object key, Object item); > } > {code} > is not compatible with JDK's 8 Map > {code} > java.util.Map { > boolean remove(Object key, Object value); > } > {code} > This causes bugs in projects, who run jdk8 and even compilation failures - > for these, who implement common's MultiMap. > *Reasoning* > JDK 8 is here and being adopted. collection-commons are not yet compatible > with Java 8. For many big project switch to commons-collections 4.x is not an > option - some transitional release version needs to be required. > Alternative would be for companies to fork commons-collections and create > their internal artifact. Why do it if the official compatibility version can > be created? > Thanks! -- This message was sent by Atlassian JIRA (v6.2#6252)