lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (SOLR-3613) Namespace Solr's JAVA OPTIONS
Date Wed, 11 Jul 2012 20:41:34 GMT


Robert Muir commented on SOLR-3613:

Supporting only Jetty? We shouldn't go there. Not supporting other app-servers is going backwards.
The customers of aforementioned Escenic Content Studio (and other applications embedding Solr)
can freely choose what app-server to run their online newspaper on (
Do you want them to stop using Solr because we "drop" support for anything but Jetty, or force
them and their customers into spinning up a Jetty process alongside their ECM? That sucks.

Its a fact we only support Jetty: its the only thing we test. I don't care about the relative
merits of app servers.
I don't care if we *should* or *should not* support anything else. I don't want to be involved
in that.

I'm just talking about what we have tests for.
This a basic fact: there are only unit tests for Jetty.

My problem is that we advertise Tomcat right on the front page, but there are no unit tests
for it,
thus encouraging users to go with an untested configuration.

I think we should just replace the word 'Tomcat' with 'Jetty' there.

> Namespace Solr's JAVA OPTIONS
> -----------------------------
>                 Key: SOLR-3613
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 4.0-ALPHA
>            Reporter: Jan H√łydahl
>             Fix For: 4.0
> Solr being a web-app, should play nicely in a setting where users deploy it on a shared
> To this regard Solr's JAVA_OPTS should be properly name spaced, both to avoid name clashes
and for clarity when reading your appserver startup script. We currently do that with most:
{{solr.solr.home,, solr.abortOnConfigurationError, solr.directoryFactory, solr.clustering.enabled,
solr.velocity.enabled etc}}, but for some opts we fail to do so.
> Before release of 4.0 we should make sure to clean this up.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message