[
https://issues.apache.org/jira/browse/CASSANDRA-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112312#comment-14112312
]
Ryan McGuire commented on CASSANDRA-7799:
-----------------------------------------
Yes, that does fix it for me. Interesting, I'm using a build from here:
https://github.com/alexkasko/openjdk-unofficial-builds
I realize that's an 'unofficial' build, but it seems to be one of the only ways
to get an openjdk from a regular tarball (I don't want to rely on system
packages, for cross-platform scripting purposes.)
> cassandra-env.sh doesn't detect openjdk version numbers
> -------------------------------------------------------
>
> Key: CASSANDRA-7799
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7799
> Project: Cassandra
> Issue Type: Bug
> Reporter: Ryan McGuire
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 2.0.11
>
> Attachments: 7799.txt
>
>
> Cassandra fails to start with openjdk with the error:
> {code}
> Cassandra 2.0 and later require Java 7u25 or later.
> {code}
> This commit broke it:
> https://github.com/apache/cassandra/commit/87548095859c210e7be8cc8bbb4a5aa1f857a6ad
> My openjdk version string looks like:
> {code}
> vagrant@cnode1:~/fab/cassandra$ java -version
> openjdk version "1.7.0-u60-unofficial"
> OpenJDK Runtime Environment (build 1.7.0-u60-unofficial-b30)
> OpenJDK 64-Bit Server VM (build 24.60-b09, mixed mode)
> {code}
> Which this change does not parse properly.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
