[
https://issues.apache.org/jira/browse/CASSANDRA-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15404749#comment-15404749
]
Robert Stupp commented on CASSANDRA-9608:
-----------------------------------------
Alright - found a (temporary) solution for the *.Cleaner issue.
But found a bug in Java9 javac: Cassandra starts using J8 + J9 if the code's
compiled with Java8 javac. But if the code's compiled with J9, it will *not*
work with J8 runtime - complains about {{java.lang.NoSuchMethodError:
java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer;}}. Verified with 1.8.0_102
+ 9-ea+128. /cc [~paul.d.san...@googlemail.com]
Steps to reproduce: With J9: {{ant realclean}} {{ant jar}}, with J8:
{{bin/cassandra}}. Seems the byte code generated by J9 is somehow wrong/broken.
> Support Java 9
> --------------
>
> Key: CASSANDRA-9608
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9608
> Project: Cassandra
> Issue Type: Task
> Reporter: Robert Stupp
> Priority: Minor
>
> This ticket is intended to group all issues found to support Java 9 in the
> future.
> From what I've found out so far:
> * Maven dependency {{com.sun:tools:jar:0}} via cobertura cannot be resolved.
> It can be easily solved using this patch:
> {code}
> - <dependency groupId="net.sourceforge.cobertura"
> artifactId="cobertura"/>
> + <dependency groupId="net.sourceforge.cobertura"
> artifactId="cobertura">
> + <exclusion groupId="com.sun" artifactId="tools"/>
> + </dependency>
> {code}
> * Another issue is that {{sun.misc.Unsafe}} no longer contains the methods
> {{monitorEnter}} + {{monitorExit}}. These methods are used by
> {{o.a.c.utils.concurrent.Locks}} which is only used by
> {{o.a.c.db.AtomicBTreeColumns}}.
> I don't mind to start working on this yet since Java 9 is in a too early
> development phase.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
