lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] Commented: (SOLR-1647) Remove the option of setting solrconfig from web.xml
Date Tue, 29 Dec 2009 02:48:30 GMT


Yonik Seeley commented on SOLR-1647:

bq. I'd also like to be more clear on what deprecation means in Solr - I know it doesn't mean
deprecating and removing before a release even goes out (that makes no sense) - and I'm not
sure if it means removing in the next dot release (as Ive see that occurring recently). Can
someone pipe in on whether Solr has an (in)formal policy on when deprecations should/can be

We don't really have a policy, but it's been a low priority to remove deprecations if they
don't get in the way.  I think it would depend a lot on what was deprecated (how expert-level
or not).

Specific to this feature,  if it isn't causing problems with development of other features,
there's no reason to not deprecate it first.

> Remove the option of setting solrconfig from web.xml
> ----------------------------------------------------
>                 Key: SOLR-1647
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Noble Paul
>            Assignee: Noble Paul
>             Fix For: 1.5
>         Attachments: SOLR-1647.patch
> with SOLR-1621 , it is not required to have an option to set solrconfig from web.xml.
Moreover editing web.xml means hacking solr itself. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message