Thanks Shawn, this makes a lot of sense.
With WAR going away and no mention of Solr deployment strategy (see:
https://cwiki.apache.org/confluence/display/solr/Taking+Solr+to+Production)
isn't good; there is a gab in Solr's release. It feels as if Solr 5.x was
rushed out ignoring Windows Servers de
On 4/16/2015 2:07 PM, Steven White wrote:
> In my case, I have to deploy Solr on Windows, AIX, and Linux (all server
> edition). We are a WebSphere shop, moving away from it means I have to
> deal with politics and culture.
You *can* run Solr 5.0 (and 5.1) in another container, just like you
coul
Thanks Karl.
In my case, I have to deploy Solr on Windows, AIX, and Linux (all server
edition). We are a WebSphere shop, moving away from it means I have to
deal with politics and culture.
For Windows, I cannot use NSSM so I have to figure a solution managing Solr
(at least start-up and shutdown
I asked a very similar question recently. You should switch to using the
package as is and forget that it contains a .war. The war is now an
internal component. Also switch to the new script for startup etc.
I have seen several disappointed users that disagree with this decision but
I assume the p
Hi folks,
With Solr 5.0, the WAR file is deprecated and I see Jetty is included with
Solr. What if I have my own Web server into which I need to deploy Solr,
how do I go about doing this correctly without messing things up and making
sure Solr works? Or is this not recommended and Jetty is the w
