[
https://issues.apache.org/jira/browse/COLLECTIONS-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000469#comment-14000469
]
Thomas Neidhart edited comment on COLLECTIONS-527 at 5/16/14 11:09 PM:
-----------------------------------------------------------------------
We could release a commons-collections 3.x version with different maven
coordinates and package name for java 8 compatibility.
But in any case, projects would have to adopt and I doubt that there are so
many changes required to upgrade to collections 4 as claimed.
Edit: a drop-in replacement as requested by the OP is simply impossible as sebb
and Joerg have pointed out.
was (Author: tn):
We could release a commons-collections 3.x version with different maven
coordinates and package name for java 8 compatibility.
But in any case, projects would have to adopt and I doubt that there are so
many changes required to upgrade to collections 4 as claimed.
> 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.
> *Compilation Error*
> If anyone implement MultiMap in their code, compilation fails with the error:
> {code}
> MyMultiHashMap.java:[11,7] error: remove(Object,Object) in MultiHashMap
> cannot implement remove(Object,Object) in Map
> [ERROR] return type Object is not compatible with boolean
> {code}
> *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)
