[
https://issues.apache.org/jira/browse/COLLECTIONS-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999906#comment-13999906
]
Ignat Alexeyenko commented on COLLECTIONS-527:
----------------------------------------------
[~joehni], thanks for your reply.
It's a breaking change indeed, but workaround is to publish a new major version
(e.g. 3.3.0).
Regarding making the situation even worse - why?
For people who need to migrate to JDK 8 and use collections 3.x, they need to:
# Fork the library
# Update their codebase (e.g. places, where MultiMap is implemented or
remove(Object, Object) is used).
Instead, if they do have a version which is Java 8 compatible - they need to go
with *2* and only update their codebase.
There might be other libraries that depends on commons-collections, but they
will not target compatibility with some fork. It's more realistic other
libraries will publish their compat-changes with respect to commons-collections
_only_ when original commons-collections publish a Java 8 compat changes.
Thanks!
> 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)
