[
https://issues.apache.org/jira/browse/CASSANDRA-6396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-6396:
----------------------------------------
Attachment: 6396.txt
I think the best thing to do is just search the default-jvm path. If the user
hasn't set up alternatives correctly, they can fix that. If they want to use a
specific non-default jvm, they can override JAVA_HOME in /etc/default/cassandra.
> debian init searches for jdk6 explicitly
> ----------------------------------------
>
> Key: CASSANDRA-6396
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6396
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 2.0.4
>
> Attachments: 6396.txt
>
>
> When JAVA_HOME isn't set, the init looks for jdk6 explicitly. Obviously for
> 2.0+ this can cause problems.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
