You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Eric Evans (JIRA)" <ji...@apache.org> on 2009/12/01 17:56:20 UTC
[jira] Assigned: (CASSANDRA-589) cassandra/bin scripts - do not
assume JAVA_HOME is going to be set in production environments
[ https://issues.apache.org/jira/browse/CASSANDRA-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Evans reassigned CASSANDRA-589:
------------------------------------
Assignee: Kay Kay
> cassandra/bin scripts - do not assume JAVA_HOME is going to be set in production environments
> ----------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-589
> URL: https://issues.apache.org/jira/browse/CASSANDRA-589
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.4
> Environment: *nix
> Reporter: Kay Kay
> Assignee: Kay Kay
> Priority: Minor
> Fix For: 0.5
>
> Attachments: CASSANDRA-589.patch
>
>
> The script cassandra assumes JAVA_HOME is already set while invoking the shell or 'java' command is present in the command-line.
> More often than not - in production - either of them are not good assumptions to make.
> Luckily - cassandra provides a way to initialize some scripts in a separate file called cassandra.in.sh .
> A better way would be to set JAVA_HOME in cassandra.in.sh , explicitly by the sys. admin / programmer .
> Assuming that is the case - ./cassandra and ./cassandra-cli need to be modified to make sure it picks up the same.
> Patch attached herewith.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.