[ https://issues.apache.org/jira/browse/CASSANDRA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230121#comment-14230121 ]
Michael Shuler commented on CASSANDRA-8315: ------------------------------------------- What Cassandra version? (I was also testing -ea releases recently on 2.1 branch for another bug and didn't have a problem, so maybe this is something earlier?) > cassandra-env.sh doesn't handle correctly non numeric JDK versions > ------------------------------------------------------------------ > > Key: CASSANDRA-8315 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8315 > Project: Cassandra > Issue Type: Bug > Reporter: Michaël Figuière > Priority: Trivial > > Trying to work around a JDK bug, I've installed a Early Access release of the > JDK, which lead to a small, non-blocking error, in {{cassandra-env.sh}} as it > expects the patch part of the JDK version to be a number, but on Oracle EA > JDKs, the patch number is followed by an {{-ea}} qualifier as in: > {code} > $ java -version > java version "1.7.0_80-ea" > Java(TM) SE Runtime Environment (build 1.7.0_80-ea-b02) > Java HotSpot(TM) 64-Bit Server VM (build 24.80-b07, mixed mode) > {code} > This lead to the following error: > {code} > bin/../conf/cassandra-env.sh: line 102: [: 80-ea: integer expression expected > {code} > Obviously not a big deal, but we may want to cover this corner case properly > by just ignoring the qualifier part of the version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)