[
https://issues.apache.org/jira/browse/SOLR-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786454#action_12786454
]
Mark Miller commented on SOLR-1621:
-----------------------------------
bq. And the user will be conscious about the existence of solr.xml .
They will be aware because we will include it with example.
bq. So technically they don't 'add' it.
New users won't add it, but old users will have to it - generally with no
benefit. If you are just running single core, being conscious of solr.xml is
not very useful. Forcing older users to add the file, just to make them
conscious off it, is not very persuasive in my opinion. Its more config for the
user with no benefit.
bq. Anyway this is a minor technicality
Its something that we will have to come to consensus on.
> Deprecate deployments w/o solr.xml
> ----------------------------------
>
> Key: SOLR-1621
> URL: https://issues.apache.org/jira/browse/SOLR-1621
> Project: Solr
> Issue Type: New Feature
> Affects Versions: 1.5
> Reporter: Noble Paul
> Fix For: 1.5
>
>
> supporting two different modes of deployments is turning out to be hard. This
> leads to duplication of code. Moreover there is a lot of confusion on where
> do we put common configuration. See the mail thread
> http://markmail.org/message/3m3rqvp2ckausjnf
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
