I am for replacing Jetty with Tomcat since Tomcat is more stable. So when a trouble is reported we can concentrate on Solr itself rather than also making sure the problem is not caused by Jetty. Besides, it seems to be a number of folks are taking the example/tutorial as is as a starting point and build upon it instead of deploying Solr into their own container. It will be a plus for those who are less familiar with setting up a container.
Bill On 6/20/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: bin/catalina.sh run, and you see the log messages in the current : window, and you can exit with CRTL-C. : So perhaps we could have our own start script that figured out the : current solr home, sets it via JAVA_OPTS, and calls "bin/catalina.sh : run" I dunno... it already bugs me a little that the example/tutorial rely on on sh/curl, and have to have that disclaimer about Cygwin that's made more then one person assume cygwin was required to use Solr on windows. I've been thinking that once we figured out where/how to commit SOLR-20 it would be really nice to use "java -jar post.jar exampledocs/*" instead of the current "sh exampledocs/post.sh exampledocs/*" ... adding another shell script just moves us away from that. .,.then again, having an example setup that breaks on non ascii characters and simple XML escaping is anoying too ... I guess I'm a +0 on the issue of switching to tomcat with a custom start script. -Hoss
