Description
Currently we default to java util logging and it's terrible in my opinion.
*It's simple built in logger is a 2 line logger.
*You have to jump through hoops to use your own custom formatter with jetty - either putting your class in the start.jar or other pain in the butt solutions.
*It can't roll files by date out of the box.
I'm sure there are more issues, but those are the ones annoying me now. We should switch to log4j - it's much nicer and it's easy to get a nice single line format and roll by date, etc.
If someone wants to use JUL they still can - but at least users could start with something decent.
Attachments
Attachments
Issue Links
- breaks
-
SOLR-5950 In SolrJ's Maven Dependency Graph, slf4j-api is optional, which breaks plain solrj users
- Closed
- incorporates
-
SOLR-3358 Capture Logging Events from JUL and Log4j
- Resolved
- is depended upon by
-
SOLR-4651 Remove -excl-slf4j build targets from trunk
- Closed
- is related to
-
SOLR-3979 slf4j bindings other than jdk -- cannot change log levels
- Closed
-
SOLR-5951 SolrDispatchFilter no longer displays useful error message on statup when logging jars are missing
- Closed
-
SOLR-3399 distribute/assume log4j logging rather then JUL
- Resolved
-
SOLR-2487 Do not include slf4j-jdk14 jar in WAR
- Closed
-
SOLR-4129 Solr UI doesn't support log4j
- Closed
- relates to
-
SOLR-4768 The Solr war produced by generate-maven-artifacts should not contain logging jars
- Closed
-
SOLR-4771 Throw a more specific exception when SLF4J logging jars cannot be found on the classpath.
- Closed
-
SOLR-4766 smoketester to check war files have the same contents
- Closed