[
https://issues.apache.org/jira/browse/SOLR-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048559#comment-13048559
]
David Smiley commented on SOLR-2586:
------------------------------------
Rob, I should have predicted you would respond to my example; I know you care
very much about the Unicode bugs. It's not that I don't care at all (although
admittedly it's low priority for me); the point is more that a unicode bug in
one servlet engine (Jetty) shouldn't mean we can't recommend people use the WAR
file and deploy it to a servlet engine -- generally speaking. Is Tomcat
_configured correctly_ a problem? Resin?
Uwe, you are apparently a fan of Jetty and that's great. I sincerely think
it's a great servlet engine. There will always be people who will overcome the
lack of certain conveniences (e.g. out of the box OS startup/shutdown hooks) to
use their preferred software, whatever it may be for whatever reason.
"configuring it right" IMO is where READMEs come in. A dedicated README for
configuring specific servlet engines, should come with Solr (Yes I do know the
info is in our Wiki). Uwe, I think you are far outnumbered by the people who
would prefer operational familiarity & setup convenience.
I agree users should avoid deploying multiple apps in the same JVM -- and just
because you might want to use an Ubuntu OS level package does not imply that
you will do that. Heck, I could deploy an app to /example/webapps/ if I wanted
to.
Any way, I'm 0 for 3 and I'll shut up now. If /example/ is operationally ready
and the recommended production install, isn't it misnamed?
> example work & logs directories needed?
> ---------------------------------------
>
> Key: SOLR-2586
> URL: https://issues.apache.org/jira/browse/SOLR-2586
> Project: Solr
> Issue Type: Improvement
> Components: Build
> Reporter: David Smiley
> Priority: Minor
>
> Firstly, what prompted this issue was me wanting to use a git solr mirror but
> finding that git's lack of empty-directory support made the "example" ant
> task fail. This task requires examples/work to be in place so that it can
> delete its contents. Fixing this was a simple matter of adding:
> {code:xml}
> <mkdir dir="${example}/work" /><!-- in case not there -->
> {code}
> Right before the delete task.
> But then it occurred to me, why even have a "work" directory since Jetty will
> apparently use a temp directory instead. -- try for yourself (stdout snippet):
> bq. 2011-06-11 00:51:26.177:INFO::Extract
> file:/SmileyDev/Search/lucene-solr/solr/example/webapps/solr.war to
> /var/folders/zo/zoQJvqc9E0076p0THiri+k+++TI/-Tmp-/Jetty_0_0_0_0_8983_solr.war__solr__k1kf17/webapp
> On my Mac, this same directory was used for multiple runs, so somehow Jetty
> or the VM figures out how to reuse it.
> Since this "example" setup isn't a *real* installation -- it's just for
> demonstration, arguably it should not contain what it doesn't need.
> Likewise, perhaps the empty example/logs directory should be deleted. It's
> not used by default any way.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
