[
https://issues.apache.org/jira/browse/SOLR-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543495#comment-13543495
]
Michael Garski commented on SOLR-3900:
--------------------------------------
I have some time available and was going to start working on this (I have a
custom logback watcher), however I noticed more than once on the mailing list
that there is a desire to move away from using solr.xml and instead determining
the cores by walking the directories. Would solr.xml still exist in this case
but only for configuring application-level items such as a LogWatcher and not
contain any core info?
> LogWatcher Config Not Persisted
> --------------------------------
>
> Key: SOLR-3900
> URL: https://issues.apache.org/jira/browse/SOLR-3900
> Project: Solr
> Issue Type: Bug
> Components: multicore
> Affects Versions: 4.0, 4.1
> Reporter: Michael Garski
> Priority: Minor
>
> When the solr.xml file is set to persistent="true", the logging element that
> contains the LogWatcher configuration is not persisted to the new solr.xml
> file that is written when managing the cores via core admin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
