Likewise, when I'm running solr as it was designed it is running on
its own where everything is tuned for solr.
The "lets change the logging" discussion only makes sense in the
infrequent (but I think important) case where you are using solr as
one element of an embedded application and need to integrate the
various logging choices of multiple components.
Max - I understand and agree with your desire to move away from
java.util.logging... but given that it works fine for the most common
usage, and the understandable resistance to changing something that
works, the minority (you, me, ken?) can deal with JDK logging until it
is a Real problem for More people.
If you have an specific issues getting the solr + JDK logging to work,
I'm sure folk can help out.
best
ryan
On 4/2/07, Erik Hatcher <[EMAIL PROTECTED]> wrote:
And likewise for my work with Solr as well.
Erik
On Apr 2, 2007, at 11:03 AM, Yonik Seeley wrote:
> On 4/2/07, Maximilian Hütter <[EMAIL PROTECTED]> wrote:
>> I believe that Solr is never run
>> completely independent of other applications, as it would be rather
>> pointless to have a search server running "stand-alone".
>
> Running as a standalone server in it's own servlet container is the
> norm for Solr usage as CNET.
>
> -Yonik
