[
https://issues.apache.org/jira/browse/SOLR-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789988#action_12789988
]
Noble Paul commented on SOLR-1621:
----------------------------------
bq.Personally, I'd prefer a form of deprecation first.
me too. But this looked like an exception. This is rarely used (if at all) and
according to me is a bad feature because it needs editing web.xml .
bq.At a minimum, it needs to be its own issue so that the warning to users that
they need to change what they are doing is very clear.
There is another issue now SOLR-1647 .I should change the language. they are
really not deprecations.
Ok . I can go both ways on this. we can keep the feature deprecated and remove
it later or remove it right away. My preference would be to remove it.
> Allow current single core deployments to be specified by 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
>
> Attachments: SOLR-1621.patch, SOLR-1621.patch, SOLR-1621.patch,
> SOLR-1621.patch, SOLR-1621.patch, SOLR-1621.patch, SOLR-1621.patch,
> SOLR-1621.patch, SOLR-1621.patch
>
>
> 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.
