[
https://issues.apache.org/jira/browse/SOLR-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786449#action_12786449
]
Noble Paul commented on SOLR-1621:
----------------------------------
bq. what are the supporting reasons?
It gives transparency. And the user will be conscious about the existence of
solr.xml . like tomcat offers the default web.xml which users usually don't
edit. But tells the users that it exists and certain behaviour is driven from
that .
Users usually take the example and make the necessary changes. So technically
they don't 'add' it. Anyway this is a minor technicality.
> 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.
