[
https://issues.apache.org/jira/browse/SOLR-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786051#action_12786051
]
Mark Miller commented on SOLR-1621:
-----------------------------------
I wrote a little patch trying this out -
One of the minor issues is that the default page that shows all of the cores
doesn't care about aliases - I think thats something we should address -
add a getNonAliasCores (with a different name) or something. Otherwise you see
the following on the index.jsp page:
Welcome to Solr!
Admin DEFAULT_CORE
Admin DEFAULT_CORE
Based on the feedback in the discussion that spawned this, we should also
consider not deprecating solr.xml. I think we should
put one in the default example, but continue supporting no solr.xml without
deprecation. If a user is not going to customize anything,
we don't gain much by forcing them to add the default solr.xml that we can
assume anyway - and we still get all of the advantages of this issue.
> 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.
