[
https://issues.apache.org/jira/browse/SOLR-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390891#comment-14390891
]
Timothy Potter commented on SOLR-7240:
--------------------------------------
Mak has proposed a solution for this:
https://gist.github.com/makuk66/20c736ae47fc4993c461
However, here's [[email protected]] take on this:
"As of solr5 we very clearly document that the only supported way to run solr
is bin/solr - we may not have ever explicitly said start.jar was no longer
supported, but we shouldn't have ever needed to because it was never officially
supported either - it was just an *example* of how to run solr in jetty.
If we're going to hold back on stuff like this now, I don't see how were ever
going to leave ourselves enough room to gradually replace the internals like
we've talked about for a while, unless we commit to rolling our own start.jar
I won't stand in the way if people think this is important, but I give up on
trying to move past "solr is just a web app" if we worry about stuff like this."
> redirect / to /solr
> --------------------
>
> Key: SOLR-7240
> URL: https://issues.apache.org/jira/browse/SOLR-7240
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Assignee: Timothy Potter
> Priority: Blocker
> Fix For: Trunk, 5.1
>
> Attachments: SOLR-7240.patch, SOLR-7240_trunk.patch
>
>
> Prior to Solr 5, we avoided doing anything fancy with our jetty configs
> because we didn't want to overly customize "the example" beyond things that
> involved loading the solr.war.
> That's not longer an issue, so we might as well plop in some jetty config
> features to redirect / to /solr.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
