[
https://issues.apache.org/jira/browse/CASSANDRA-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857806#action_12857806
]
Hudson commented on CASSANDRA-971:
----------------------------------
Integrated in Cassandra #408 (See
[http://hudson.zones.apache.org/hudson/job/Cassandra/408/])
simplify configuration file loading; rename to cassandra.xml
patch by jbellis; reviewed by eevans for CASSANDRA-971
> simplify configuration file loading
> -----------------------------------
>
> Key: CASSANDRA-971
> URL: https://issues.apache.org/jira/browse/CASSANDRA-971
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.7
>
> Attachments: 971.txt
>
>
> Currently we can load the configuration file from (a) a full path specified
> by -Dstorage-config, or (b) "storage.conf.xml" located anywhere on the
> classpath (filename may not be changed).
> I think we should figure out what The Right Thing is to do here, and then do
> it, instead of trying multiple guesses in an effort to prevent ... what?
> ISTM that the java idiom here is, look for a default filename on the
> classpath, and allow customizing that name w/ a system property, but when
> taking the property ONLY the filename is customized, not the full path. This
> is what log4j does, for instance.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira