[
https://issues.apache.org/jira/browse/SOLR-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710370#comment-13710370
]
Erick Erickson commented on SOLR-3633:
--------------------------------------
[~steffkes]
Doesn't work for me, what did I miss?
I took a stock trunk (and 4x, results identical). Renamed
example/solr/collection1/core.properties to "eoe.properties". Now going to
http://localhost:8983/solr/ still displays the big red box..... Or is that
intended and I just don't understand? I did do an 'ant clean' from the top
level and rebuilt...
> web UI reports an error if CoreAdminHandler says there are no SolrCores
> -----------------------------------------------------------------------
>
> Key: SOLR-3633
> URL: https://issues.apache.org/jira/browse/SOLR-3633
> Project: Solr
> Issue Type: Bug
> Components: web gui
> Affects Versions: 4.0-ALPHA
> Reporter: Hoss Man
> Assignee: Stefan Matheis (steffkes)
> Fix For: 5.0, 4.5
>
> Attachments: SOLR-3633.patch, SOLR-3633.patch, SOLR-3633.patch,
> SOLR-3633.patch, SOLR-3633.patch, SOLR-3633.patch
>
>
> Spun off from SOLR-3591...
> * having no SolrCores is a valid situation
> * independent of what may happen in SOLR-3591, the web UI should cleanly deal
> with there being no SolrCores, and just hide/grey out any tabs that can't be
> supported w/o at least one core
> * even if there are no SolrCores the core admin features (ie: creating a new
> core) should be accessible in the UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
