[ https://issues.apache.org/jira/browse/HBASE-10030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875132#comment-13875132 ]
Andrew Purtell edited comment on HBASE-10030 at 1/17/14 7:18 PM: ----------------------------------------------------------------- bq. Java version: 1.8.0-ea, vendor: Oracle Corporation Ok, I am sorry, I have not adequately explained what we did here. We deprecated the old method but did not remove it. Therefore at some point we can kill the conflicting method, I guess we can do this in trunk now that 0.98 is branched, and *then* we can compile with JDK 8. Edit: Also, above, I forgot I have this removal applied privately to the branch I use for JDK 8 stuff. Sorry again. was (Author: apurtell): bq. Java version: 1.8.0-ea, vendor: Oracle Corporation Ok, I am sorry, I have not adequately explained what we did here. We deprecated the old method but did not remove it. Therefore at some point we can kill the conflicting method, I guess we can do this in trunk now that 0.98 is branched, and *then* we can compile with JDK 8. > [JDK8] Erasure of PoolMap#remove(K,V) conflicts with superclass method > ---------------------------------------------------------------------- > > Key: HBASE-10030 > URL: https://issues.apache.org/jira/browse/HBASE-10030 > Project: HBase > Issue Type: Bug > Reporter: Andrew Purtell > Assignee: Andrew Purtell > Priority: Trivial > Fix For: 0.98.0 > > Attachments: 10030.patch > > > On JDK 8, the erasure of PoolMap#remove(K,V) conflicts with superclass method > remove(Object,Object). -- This message was sent by Atlassian JIRA (v6.1.5#6160)