You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Nick Bailey (JIRA)" <ji...@apache.org> on 2010/08/02 23:58:18 UTC
[jira] Created: (CASSANDRA-1347) Move JVM_OPTS from cassandra.in.sh
to the conf directory
Move JVM_OPTS from cassandra.in.sh to the conf directory
--------------------------------------------------------
Key: CASSANDRA-1347
URL: https://issues.apache.org/jira/browse/CASSANDRA-1347
Project: Cassandra
Issue Type: Improvement
Components: Packaging
Affects Versions: 0.6.3
Reporter: Nick Bailey
Assignee: Nick Bailey
Priority: Minor
Fix For: 0.7.0
Configuring the jvm options from the cassandra.in.sh script doesn't really make sense from a packaging perspective. These should exist in the conf directory and be overridden by deployment specific packages.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1347) Move JVM_OPTS from
cassandra.in.sh to the conf directory
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896355#action_12896355 ]
Hudson commented on CASSANDRA-1347:
-----------------------------------
Integrated in Cassandra #510 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/510/])
move JVM_OPTS from cassandra.in.sh to the conf/ dir
Patch by Nick Bailey; review by eevans for CASSANDRA-1347
> Move JVM_OPTS from cassandra.in.sh to the conf directory
> --------------------------------------------------------
>
> Key: CASSANDRA-1347
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1347
> Project: Cassandra
> Issue Type: Improvement
> Components: Packaging
> Affects Versions: 0.6.3
> Reporter: Nick Bailey
> Assignee: Nick Bailey
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: configuration-improvements.txt
>
>
> Configuring the jvm options from the cassandra.in.sh script doesn't really make sense from a packaging perspective. These should exist in the conf directory and be overridden by deployment specific packages.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-1347) Move JVM_OPTS from cassandra.in.sh
to the conf directory
Posted by "Nick Bailey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Bailey updated CASSANDRA-1347:
-----------------------------------
Attachment: configuration-improvements.txt
Moved jvm options to conf/cassandra-env.sh
I also made a few minor changes that make packaging and the init.d script in contrib work well together.
Assuming this change is approved I don't see why debian/cassandra.in.sh needs to exist anymore. A debian specific jvm configuration could exist in conf or contrib perhaps.
> Move JVM_OPTS from cassandra.in.sh to the conf directory
> --------------------------------------------------------
>
> Key: CASSANDRA-1347
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1347
> Project: Cassandra
> Issue Type: Improvement
> Components: Packaging
> Affects Versions: 0.6.3
> Reporter: Nick Bailey
> Assignee: Nick Bailey
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: configuration-improvements.txt
>
>
> Configuring the jvm options from the cassandra.in.sh script doesn't really make sense from a packaging perspective. These should exist in the conf directory and be overridden by deployment specific packages.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.