Shawn Heisey commented on SOLR-12059:

Based on all of the "rename" questions the reporter has asked on the mailing 
list (including this one), I think they are trying to install Solr for a 
customer and remove all names and other evidence that the software is Solr.

The level of customization required to achieve this goal is *very* high, and 
would need to be repeated for every version upgrade.

If this is the user's goal, the question we have to ask ourselves before we 
"fix" this issue:  How much help are we willing to give to somebody in removing 
an Apache Foundation trademark from the software?  From a legal perspective, 
the trademarks are BIG part of the power the foundation has to enforce its 
goals.  The foundation can't *prevent* anyone from removing the trademarks, and 
I wouldn't want to even if we did have that power, but I don't think we should 
spend any time helping.

> 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

To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to