[
https://issues.apache.org/jira/browse/SOLR-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786407#action_12786407
]
Mark Miller commented on SOLR-1621:
-----------------------------------
bq. It is better to be consistent in the long run.
Why - what are the supporting reasons? Making current users put in a boiler
plate file in the future doesn't appear to have any benefits to me. If they
want to use settings in the file, they can add the file, but just to add it for
the sake of adding it is not very appealing.
> 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.
