You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by Maximilian Hütter <mh...@blue-elephant-systems.com> on 2007/03/29 09:36:23 UTC
Changing Logging in Solr to Apache Commons Logging
Hi everybody,
as I see in the source code, Solr uses JDK-Logging. How about changing
that to Apache Commons Logging?
Best regards,
Max Hütter
--
Maximilian Hütter
blue elephant systems GmbH
Wollgrasweg 49
D-70599 Stuttgart
Tel : (+49) 0711 - 45 10 17 578
Fax : (+49) 0711 - 45 10 17 573
e-mail : max.huetter@blue-elephant-systems.com
Sitz : Stuttgart, Amtsgericht Stuttgart, HRB 24106
Geschäftsführer: Joachim Hörnle, Thomas Gentsch, Holger Dietrich
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
I'm -1 on Commons Logging based on many JARmegaddon experiences with
other libraries that used it and getting all the dependencies
straightened out.
JDK logging suits me fine in Solr.
Erik
On Mar 29, 2007, at 6:59 PM, Chris Hostetter wrote:
>
> : yes it would be nice if there configuration could be easier
> because all
> : applications used the same logging framework, but i see no reason to
> : assume that every other application people are using is using
> : commons-logging ... jdk logging is simple and standardized: it is by
> : definition included in every java 1.5 servlet container in existence
> : because it is by definiteion included in every java 1.5 jvm ... i
> can't
> : really see a reason to change a lot of code to use a logging
> framework
> : that *adds* a new dependency.
>
> Since i would by no means consider myself an expert on commons-
> logging, i
> wanted to do a little research to ensure that I wasn't missing
> osmething
> really obvious abotu why we *should* be using commons-logging.
>
> I freely admit, I didn't appricate how much commons-logging is
> intended to
> be a middle-layer API for other arbitrary logging frameworks like JDK
> logging or log4j, but i still don't think it makes sense to switch,
> particulararly given the last paragraph of this wiki...
>
> http://wiki.apache.org/jakarta-commons/Commons_Logging_FUD
>
>
>
>
>
> -Hoss
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Mike Klaas <mi...@gmail.com>.
On 3/30/07, Maximilian Hütter <mh...@blue-elephant-systems.com> wrote:
> Chris Hostetter schrieb:
>
> > I freely admit, I didn't appricate how much commons-logging is intended to
> > be a middle-layer API for other arbitrary logging frameworks like JDK
> > logging or log4j, but i still don't think it makes sense to switch,
> > particulararly given the last paragraph of this wiki...
> >
> > http://wiki.apache.org/jakarta-commons/Commons_Logging_FUD
>
> As you saw using commons-logging is not just another logging framework,
> but would allow to use basically any framework you would like.
If this were the only consequence, it might be worth pursuing. The
inherent classloader issues to providing that functionality seem to
have caused many other people much difficulty:
http://www.qos.ch/logging/thinkAgain.html
> Actually I see the argument made in the last paragraph very much in
> favor of using it in Solr. Solr is intended to be used with other
> applications, which will very likely use different logging frameworks.
I don't think so--the author of commons-logging recommended it only
for small pieces of code used by other applications. Solr is closer
to a stand-alone application/server.
-1.
-Mike
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
On Mar 30, 2007, at 4:49 AM, Maximilian Hütter wrote:
> The added dependency is just one jar (apache project too), which is
> not
> a to high price to pay for the benefits pointed out before.
I can say with first hand experience that Commons Logging has caused
more pain than it was worth in terms of conflicting with other
applications.
I think you'd need to come up with a specific concrete example of
where Commons Logging adds benefit before we'd consider switching to it.
Erik
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
For those of you that feel very strongly about swapping out logging
frameworks, give AOP (such as AspectJ) a try to hook the logging. I
suspect it'd be possible to write a few AOP rules that would swap it
out nicely.
Erik
On Apr 2, 2007, at 5:43 PM, Chris Hostetter wrote:
>
> : But Solr will in most cases run together with other applications
> in a
> : webcontainer. So Solr is not really a stand-alone application in
> that sense.
> : As other here have pointed out, they have same problems of having to
> : support different logging configurations.
>
> I would disagree with saying "most cases", and the problems other
> people
> have refered to are some people who are doing fairly novel things with
> Solr embeded in their aplications - those same people (definitely
> Ken, i
> think i saw a reply to this effect from Ryan) also point out that when
> using Solr as a webapp, their servlet takes care of the disjoint
> logging
> framework issues for them.
>
> : completely independent of other applications, as it would be rather
> : pointless to have a search server running "stand-alone". Sure you
> can
> : integrate Solr with other software not even written in java, but
> still
> : many people will integrate it with other java applications
> running in
> : the same webcontainer.
>
> i would *strenously* disagree with you there ... i have have talked
> with
> lots of people running Solr and i don't know anyone running it in
> the same
> JVM as another application in a production situation.
>
> : Of course your are right, JDK logging can be configured in other
> ways,
> : what I wanted to point out is that JDK logging is configured per VM
> : which is less flexible than for example Log4J (correct me if I'm
> wrong).
>
> There's a differnece between configuring it per JRE installation
> and per
> JVM process instance ... even in the later case, the "major" servlet
> containers already take care of letting you have seperate
> configuration
> per webapp/WAR.
>
> : So you are suggesting that I write my own wrapper for the JDK
> logging,
> : but as I see it this is what Commons-logging is about, having a
> wrapper
> : to use different logging frameworks.
>
> No, that comment was more generally about why I don't understand the
> appeal of moving towards a third party logging abstraction now that a
> logging abstraction already exists in the core langauge -- I
> suspect that
>
> Ultimately my main point is that all Servlet Containers already
> *have* to
> deal with JDK logging -- it is 100% safe to use, we don't have to
> worry
> about dependencies, or classpath issues; the Container takes care
> of all
> that. Further: many servlet containers *also* make dealing with
> code that uses multiple logging frameworks painless and
> configurable in a
> singlurar way -- they are already solving that problem for
> applications
> in general, so we don't really need to go out of our way to do
> anything
> special for Solr.
>
>
>
> -Hoss
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Chris Hostetter <ho...@fucit.org>.
: But Solr will in most cases run together with other applications in a
: webcontainer. So Solr is not really a stand-alone application in that sense.
: As other here have pointed out, they have same problems of having to
: support different logging configurations.
I would disagree with saying "most cases", and the problems other people
have refered to are some people who are doing fairly novel things with
Solr embeded in their aplications - those same people (definitely Ken, i
think i saw a reply to this effect from Ryan) also point out that when
using Solr as a webapp, their servlet takes care of the disjoint logging
framework issues for them.
: completely independent of other applications, as it would be rather
: pointless to have a search server running "stand-alone". Sure you can
: integrate Solr with other software not even written in java, but still
: many people will integrate it with other java applications running in
: the same webcontainer.
i would *strenously* disagree with you there ... i have have talked with
lots of people running Solr and i don't know anyone running it in the same
JVM as another application in a production situation.
: Of course your are right, JDK logging can be configured in other ways,
: what I wanted to point out is that JDK logging is configured per VM
: which is less flexible than for example Log4J (correct me if I'm wrong).
There's a differnece between configuring it per JRE installation and per
JVM process instance ... even in the later case, the "major" servlet
containers already take care of letting you have seperate configuration
per webapp/WAR.
: So you are suggesting that I write my own wrapper for the JDK logging,
: but as I see it this is what Commons-logging is about, having a wrapper
: to use different logging frameworks.
No, that comment was more generally about why I don't understand the
appeal of moving towards a third party logging abstraction now that a
logging abstraction already exists in the core langauge -- I suspect that
Ultimately my main point is that all Servlet Containers already *have* to
deal with JDK logging -- it is 100% safe to use, we don't have to worry
about dependencies, or classpath issues; the Container takes care of all
that. Further: many servlet containers *also* make dealing with
code that uses multiple logging frameworks painless and configurable in a
singlurar way -- they are already solving that problem for applications
in general, so we don't really need to go out of our way to do anything
special for Solr.
-Hoss
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Ryan McKinley <ry...@gmail.com>.
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 <er...@ehatchersolutions.com> 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 <mh...@blue-elephant-systems.com> 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
>
>
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
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 <mh...@blue-elephant-systems.com> 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
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Yonik Seeley <yo...@apache.org>.
On 4/2/07, Maximilian Hütter <mh...@blue-elephant-systems.com> 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
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Maximilian Hütter <mh...@blue-elephant-systems.com>.
Chris Hostetter schrieb:
> Solr is first and foremos an application, run in an application server --
> it interacts with other applications via webservice-ish APIs, which may or
> may not even be in Java. From that standpoint, Solr does not fit
> Waldhoff's criteria: "If you're building a stand-alone application, don't
> use commons-logging"
But Solr will in most cases run together with other applications in a
webcontainer. So Solr is not really a stand-alone application in that sense.
As other here have pointed out, they have same problems of having to
support different logging configurations.
The think the basic argument still holds, that when integrating
applications Commons-logging is useful. 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". Sure you can
integrate Solr with other software not even written in java, but still
many people will integrate it with other java applications running in
the same webcontainer.
> JDK logging can be configured in a lot more ways then just a file in
> $JAVA_HOME/jre/lib ... i'm not trying to be rude here, but that comment
> leads me to believe you understand less about how JDK logging works then i
> do about how commons loggign works.
Of course your are right, JDK logging can be configured in other ways,
what I wanted to point out is that JDK logging is configured per VM
which is less flexible than for example Log4J (correct me if I'm wrong).
> specificly: JDK logging actually has
> all of hte mechanisms in it so that if you wnated to use log4j as the
> underlying implementaiton, you could do so by implementing a few classes
> and setting a system property at run time -- as i understand it, TomCat
> and many other servlet containers already do this, so that applications
> they run which use JDK logging get the log configuration from their main
> log files.
So you are suggesting that I write my own wrapper for the JDK logging,
but as I see it this is what Commons-logging is about, having a wrapper
to use different logging frameworks.
--
Maximilian Hütter
blue elephant systems GmbH
Wollgrasweg 49
D-70599 Stuttgart
Tel : (+49) 0711 - 45 10 17 578
Fax : (+49) 0711 - 45 10 17 573
e-mail : max.huetter@blue-elephant-systems.com
Sitz : Stuttgart, Amtsgericht Stuttgart, HRB 24106
Geschäftsführer: Joachim Hörnle, Thomas Gentsch, Holger Dietrich
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Ryan McKinley <ry...@gmail.com>.
>
> Since we use Resin, and Resin does support what you're describing,
> this is the approach I'm taking short-term.
In my resin setup when I run solr directly from
apache-solr-1.2-dev.war, everything is great.
>
> But for our embedded Jetty usage, I'll be back in the same situation as Ryan.
>
In a jetty+wicket environment that integrates with legacy log4j code,
I'll try a Log4J LogManager -- thanks for the pointer Chris.
> Not that I'm arguing for use of Apache Commons Logging (I've had
> enough fun with that in Nutch), just commenting on the discussion
> here.
>
I'm defiantly not promoting commons logging either! I also had less
then great experience with it. I posted the question a few weeks back
because both jetty and wicket use slf4j and i've had good luck with it
so far. If solr also used it, _my_ stack would be consistent, but I
understand I'm not running a typical setup and don't want/need to rock
the boat if changes don't help anyone else...
ryan
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Ken Krugler <kk...@transpac.com>.
>: Do you have any pointers on how to change the underlying framework? I
>: don't see anything like that in:
>: http://java.sun.com/j2se/1.4.2/docs/guide/util/logging/overview.html
>: or other obvious (google) places to look
>
>The key bit is the LogManager ... you can specify any concrete
>implementation you want using the java.util.logging.manager system
>property ... in theory you could define a Log4JLogManager that proxies to
>the various underlying log4j classes. I don't know that i've ever seen a
>robust reusbale one, but i have seen people wrap log4j handlers up so
>they can be used as JDK logging handlers.
>
>As far as i can tell, the main reason for third-party logging abstractions
>(like slf4j and commons-logging, etc..) at this point is supporting older
>JDKs and providing simplified APIs ... but i freely admit, there could be
>other benefits i'm missing.
>
>: I have been integrating solr with a legacy system tied to log4j - i
>: have two logging configurations - a pain, but obviously not that big
>: of deal.
>
>you're also in a somewhat unique scenerio becuse you aren't running Solr
>in a servlet container right?
We've run into a similar issue, where we have a mix of webapps. All
of the non-Solr guys use Log4J with a rotating daily appender, but
since this isn't supported by the default JDK logger, there's a
mismatch in log files being produced.
I'd looked at doing what you mention above (wrapping Log4J with a
LogManager), and it isn't a big deal but just a bit of an annoyance.
I did search for a reusable implementation of this and also didn't
find anything that looked good to me.
>>From what i've seen, a couple of the
>heavy hitters seem to have their own custom logging configuration
>mechanism, which appears to work regardless of wehter you are using log4j
>or jdk logging -- presumably because they implement their own LogManager
>(or equivilent) for each.
Since we use Resin, and Resin does support what you're describing,
this is the approach I'm taking short-term.
But for our embedded Jetty usage, I'll be back in the same situation as Ryan.
Not that I'm arguing for use of Apache Commons Logging (I've had
enough fun with that in Nutch), just commenting on the discussion
here.
-- Ken
--
Ken Krugler
Krugle, Inc.
+1 530-210-6378
"Find Code, Find Answers"
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Chris Hostetter <ho...@fucit.org>.
: Do you have any pointers on how to change the underlying framework? I
: don't see anything like that in:
: http://java.sun.com/j2se/1.4.2/docs/guide/util/logging/overview.html
: or other obvious (google) places to look
The key bit is the LogManager ... you can specify any concrete
implementation you want using the java.util.logging.manager system
property ... in theory you could define a Log4JLogManager that proxies to
the various underlying log4j classes. I don't know that i've ever seen a
robust reusbale one, but i have seen people wrap log4j handlers up so
they can be used as JDK logging handlers.
As far as i can tell, the main reason for third-party logging abstractions
(like slf4j and commons-logging, etc..) at this point is supporting older
JDKs and providing simplified APIs ... but i freely admit, there could be
other benefits i'm missing.
: I have been integrating solr with a legacy system tied to log4j - i
: have two logging configurations - a pain, but obviously not that big
: of deal.
you're also in a somewhat unique scenerio becuse you aren't running Solr
in a servlet container right? From what i've seen, a couple of the
heavy hitters seem to have their own custom logging configuration
mechanism, which appears to work regardless of wehter you are using log4j
or jdk logging -- presumably because they implement their own LogManager
(or equivilent) for each.
-Hoss
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Ryan McKinley <ry...@gmail.com>.
>
> I don't remember seeing any specific benefits listed except that it would
> let people choose the underlying logging framework, as i've mentioned this
> is possible with JDK logging)
>
Do you have any pointers on how to change the underlying framework? I
don't see anything like that in:
http://java.sun.com/j2se/1.4.2/docs/guide/util/logging/overview.html
or other obvious (google) places to look
A few weeks back, I suggested http://www.slf4j.org/ so that I could
choose the underlying logging framework, if this is supported directly
from java logging, all the better!
I have been integrating solr with a legacy system tied to log4j - i
have two logging configurations - a pain, but obviously not that big
of deal.
thanks
ryan
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Chris Hostetter <ho...@fucit.org>.
: Actually I see the argument made in the last paragraph very much in
: favor of using it in Solr. Solr is intended to be used with other
: applications, which will very likely use different logging frameworks.
Solr is first and foremos an application, run in an application server --
it interacts with other applications via webservice-ish APIs, which may or
may not even be in Java. From that standpoint, Solr does not fit
Waldhoff's criteria: "If you're building a stand-alone application, don't
use commons-logging"
Solr can/is also be(ing) used as a framework for JAva applications, that
want Lucene at their core, but like having some of the structure Solr
provides -- even in this standpoint, Waldhoff wdoes not seem to recommend
commons logging: "If you're building an application server, don't use
commons-logging. If you're building a moderately large framework, don't
use commons-logging."
The one case Waldhoff recommends commons logging, certainly doesn't apply
to Solr: "a tiny little component that you intend for other developers to
embed in their applications"
: applications and webcontainers. As I see it java.util.logging is
: configured through a properties file in $JAVA_HOME/jre/lib. Which not
: all that nice, other logging frameworks are more flexible to configure
: and use.
JDK logging can be configured in a lot more ways then just a file in
$JAVA_HOME/jre/lib ... i'm not trying to be rude here, but that comment
leads me to believe you understand less about how JDK logging works then i
do about how commons loggign works. specificly: JDK logging actually has
all of hte mechanisms in it so that if you wnated to use log4j as the
underlying implementaiton, you could do so by implementing a few classes
and setting a system property at run time -- as i understand it, TomCat
and many other servlet containers already do this, so that applications
they run which use JDK logging get the log configuration from their main
log files.
: The added dependency is just one jar (apache project too), which is not
: a to high price to pay for the benefits pointed out before.
I don't remember seeing any specific benefits listed except that it would
let people choose the underlying logging framework, as i've mentioned this
is possible with JDK logging)
-Hoss
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Maximilian Hütter <mh...@blue-elephant-systems.com>.
Chris Hostetter schrieb:
> I freely admit, I didn't appricate how much commons-logging is intended to
> be a middle-layer API for other arbitrary logging frameworks like JDK
> logging or log4j, but i still don't think it makes sense to switch,
> particulararly given the last paragraph of this wiki...
>
> http://wiki.apache.org/jakarta-commons/Commons_Logging_FUD
>
As you saw using commons-logging is not just another logging framework,
but would allow to use basically any framework you would like.
Actually I see the argument made in the last paragraph very much in
favor of using it in Solr. Solr is intended to be used with other
applications, which will very likely use different logging frameworks.
Using commons-logging will make Solr easier to integrate with other
applications and webcontainers. As I see it java.util.logging is
configured through a properties file in $JAVA_HOME/jre/lib. Which not
all that nice, other logging frameworks are more flexible to configure
and use.
The added dependency is just one jar (apache project too), which is not
a to high price to pay for the benefits pointed out before.
--
Maximilian Hütter
blue elephant systems GmbH
Wollgrasweg 49
D-70599 Stuttgart
Tel : (+49) 0711 - 45 10 17 578
Fax : (+49) 0711 - 45 10 17 573
e-mail : max.huetter@blue-elephant-systems.com
Sitz : Stuttgart, Amtsgericht Stuttgart, HRB 24106
Geschäftsführer: Joachim Hörnle, Thomas Gentsch, Holger Dietrich
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Chris Hostetter <ho...@fucit.org>.
: yes it would be nice if there configuration could be easier because all
: applications used the same logging framework, but i see no reason to
: assume that every other application people are using is using
: commons-logging ... jdk logging is simple and standardized: it is by
: definition included in every java 1.5 servlet container in existence
: because it is by definiteion included in every java 1.5 jvm ... i can't
: really see a reason to change a lot of code to use a logging framework
: that *adds* a new dependency.
Since i would by no means consider myself an expert on commons-logging, i
wanted to do a little research to ensure that I wasn't missing osmething
really obvious abotu why we *should* be using commons-logging.
I freely admit, I didn't appricate how much commons-logging is intended to
be a middle-layer API for other arbitrary logging frameworks like JDK
logging or log4j, but i still don't think it makes sense to switch,
particulararly given the last paragraph of this wiki...
http://wiki.apache.org/jakarta-commons/Commons_Logging_FUD
-Hoss
RE: Changing Logging in Solr to Apache Commons Logging
Posted by Daniel Pitts <Da...@cnet.com>.
> : > What would be the motivations for making such a change?
> : >
> : Solr is (mostly) used in a web-container, often together with other
> : applications. Configuration would be easier if all applications
could
> : use the same logging. In addition Apache Commons Logging can be used
> : with different logging toolkits, so Solr would be independent from a
> : specific logging framework.
> yes it would be nice if there configuration could be easier because
all
> applications used the same logging framework, but i see no reason to
> assume that every other application people are using is using
> commons-logging ... jdk logging is simple and standardized: it is by
> definition included in every java 1.5 servlet container in existence
> because it is by definiteion included in every java 1.5 jvm ... i
can't
> really see a reason to change a lot of code to use a logging framework
> that *adds* a new dependency.
That's true in a way, but commons-logging is little more than a delegate
to other frameworks. If solr used commons logging, then people could
integrate solr with log4j, jdk logging, etc... The big down side is the
added dependency.
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Chris Hostetter <ho...@fucit.org>.
: > What would be the motivations for making such a change?
: >
: Solr is (mostly) used in a web-container, often together with other
: applications. Configuration would be easier if all applications could
: use the same logging. In addition Apache Commons Logging can be used
: with different logging toolkits, so Solr would be independent from a
: specific logging framework.
yes it would be nice if there configuration could be easier because all
applications used the same logging framework, but i see no reason to
assume that every other application people are using is using
commons-logging ... jdk logging is simple and standardized: it is by
definition included in every java 1.5 servlet container in existence
because it is by definiteion included in every java 1.5 jvm ... i can't
really see a reason to change a lot of code to use a logging framework
that *adds* a new dependency.
-Hoss
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Maximilian Hütter <mh...@blue-elephant-systems.com>.
Chris Hostetter schrieb:
> : as I see in the source code, Solr uses JDK-Logging. How about changing
> : that to Apache Commons Logging?
>
> What would be the motivations for making such a change?
>
Solr is (mostly) used in a web-container, often together with other
applications. Configuration would be easier if all applications could
use the same logging. In addition Apache Commons Logging can be used
with different logging toolkits, so Solr would be independent from a
specific logging framework.
I could contribute a patch doing this.
--
Maximilian Hütter
blue elephant systems GmbH
Wollgrasweg 49
D-70599 Stuttgart
Tel : (+49) 0711 - 45 10 17 578
Fax : (+49) 0711 - 45 10 17 573
e-mail : max.huetter@blue-elephant-systems.com
Sitz : Stuttgart, Amtsgericht Stuttgart, HRB 24106
Geschäftsführer: Joachim Hörnle, Thomas Gentsch, Holger Dietrich
Re: Changing Logging in Solr to Apache Commons Logging
Posted by Chris Hostetter <ho...@fucit.org>.
: as I see in the source code, Solr uses JDK-Logging. How about changing
: that to Apache Commons Logging?
What would be the motivations for making such a change?
you may also want to review this recent related thread...
http://www.nabble.com/Re%3A-logging---slf4j--p9369105.html
-Hoss