[
https://issues.apache.org/jira/browse/SOLR-12059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16405954#comment-16405954
]
Edwin Yeo Zheng Lin commented on SOLR-12059:
--------------------------------------------
Is it that we have to change everything for those that are in code in order to
assure that Solr will work correctly?
So far I manage to get it to work by changing the hard-coded solr.xml in
SolrXmlConfig.class source code, and it is working for our common use features.
But I'm not sure if it will affect other features which we are currently not
using.
> Unable to rename solr.xml
> -------------------------
>
> Key: SOLR-12059
> URL: https://issues.apache.org/jira/browse/SOLR-12059
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 6.5.1
> Environment: Renaming of solr,xml in the $SOLR_HOME directory
> Reporter: Edwin Yeo Zheng Lin
> Priority: Major
>
> I am able to rename the flie names like solrconfig.xml and solr.log to custom
> names like myconfig.xml and my.log quite seamlessly.
> However, I am not able to rename the same for solr.xml. Understand that the
> solr.xml is hard-coded at the SolrXmlConfig.java. Meaning it requires a
> re-compile of the Jar file in order to rename it.
> Since we can rename files like solrconfig.xml from the properties files, so
> we should do the same for solr.xml?
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
