Erik Hatcher wrote:
I'm also opposed (sorry Grant) to tossing in a 3rd party library for
logging when the built-in logging facility is sufficient, configurable,
and adaptable already.
I must say I never liked JDK logging because it feels like a step back
when you are used to log4j.
So from my perspective:
* Solr is a software you mostly run on servers. So log rotation and
sending emails on errors is a must. Nothing of that is provided by the
JDK logging implementation (or does not work correctly as someone else
has stated).
* JDK logging configuration is only on JVM level. When you use many Solr
instances in one JVM (we have one per customer) and want several
different log destinations that is not possible. I want logs per
customer - that is currently not possible.
I would like to see SL4J based logging in Solr. commons-logging is no
alternative. It is meant for libraries because "commons-logging does not
attempt to initialize or terminate the underlying logging implementation
that is used at runtime; that is the responsibility of the application".
CU
Thomas
