You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2014/12/31 05:48:14 UTC
[jira] [Comment Edited] (SOLR-6792) cleanup solrconfig.xml files by
removing implicit plugins
[ https://issues.apache.org/jira/browse/SOLR-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261909#comment-14261909 ]
Noble Paul edited comment on SOLR-6792 at 12/31/14 4:48 AM:
------------------------------------------------------------
bq.And nuking the class entirely in trunk.
We should give enough time to users to cleanup their solrconfig.xml files. TIll that point we will keep the class around
bq.I also wonder if it's worth going through and removing explicit definitions from the various test and example solrconfig.xml files we have?
I think I have removed most references
was (Author: noble.paul):
bq.And nuking the class entirely in trunk.
We shold give enough time to users to cleanup their solrconfig.xml files. TIll that point we will keep the class around
bq.I also wonder if it's worth going through and removing explicit definitions from the various test and example solrconfig.xml files we have?
I think I have removed most references
> cleanup solrconfig.xml files by removing implicit plugins
> ---------------------------------------------------------
>
> Key: SOLR-6792
> URL: https://issues.apache.org/jira/browse/SOLR-6792
> Project: Solr
> Issue Type: Bug
> Reporter: Noble Paul
> Assignee: Noble Paul
> Fix For: 5.0, Trunk
>
> Attachments: SOLR-6792.patch
>
>
> /replication , /get , /update, /admin/ are registered implicitly for each core. No need to specify them from solrconfig.xml if nothing custom needs to be added
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org