You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/07/26 20:45:10 UTC

[jira] [Resolved] (CASSANDRA-2895) add java classpath to cassandra startup logging

     [ https://issues.apache.org/jira/browse/CASSANDRA-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-2895.
---------------------------------------

    Resolution: Fixed

Jackson: Okay, I'll buy that.  Committed to 0.7.8, 0.8.3, and 1.0.

Rick: that relies on stdout being captured, which isn't always the case.  (And even when it is, I'd prefer to avoid having to explain why that's in a separate file than system.log...)

> add java classpath to cassandra startup logging
> -----------------------------------------------
>
>                 Key: CASSANDRA-2895
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2895
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jackson Chung
>            Assignee: Jackson Chung
>            Priority: Minor
>             Fix For: 0.8.2, 0.7.8
>
>         Attachments: 2895.diff
>
>
> this is helpful to determine/verify if the Cassandra is started with the expected classpath
> it's a simple 1-liner addon that are useful... will submit a patch later.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira