cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Shuler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9416) 3.x should refuse to start on JVM_VERSION < 1.8
Date Sat, 23 May 2015 17:09:17 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14557434#comment-14557434
] 

Michael Shuler commented on CASSANDRA-9416:
-------------------------------------------

There was a java7 feature that we required 1.7u25 or higher in cassandra-2.0. Unless there
is some feature Cassandra is using that was added in patch level u45, no, it would not be
correct to depend on u45 or higher. I think a check of 1.8 is sufficient, unless someone knows
of a particular java8 feature that is being used from a particular patch level. For instance,
trunk currently builds and runs tests fine for me on 1.8u5. [~rogercafe] if you could update
the patch for just a 1.8 check, I think that's fine for now. Thanks!

> 3.x should refuse to start on JVM_VERSION < 1.8
> -----------------------------------------------
>
>                 Key: CASSANDRA-9416
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9416
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Michael Shuler
>            Priority: Minor
>              Labels: lhf
>             Fix For: 3.x
>
>         Attachments: trunk-9416.patch
>
>
> When I was looking at CASSANDRA-9408, I noticed that {{conf/cassandra-env.sh}} and {{conf/cassandra-env.ps1}}
do JVM version checking and should get updated for 3.x to refuse to start with JVM_VERSION
< 1.8.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message