[SOLR-3706] Ship setup to log with log4j.

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 4.3, 6.0
• Assignee: Mark Miller
• Reporter: Mark Miller
• Created: 03/Aug/12 16:50
• Updated: 09/May/16 18:52
• Resolved: 04/Apr/13 23:38

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.

Issue Links

• breaks: SOLR-5950 In SolrJ's Maven Dependency Graph, slf4j-api is optional, which breaks plain solrj users
• incorporates: SOLR-3358 Capture Logging Events from JUL and Log4j
• is depended upon by: SOLR-4651 Remove -excl-slf4j build targets from trunk
• is related to: SOLR-3979 slf4j bindings other than jdk -- cannot change log levels
• is related to: SOLR-5951 SolrDispatchFilter no longer displays useful error message on statup when logging jars are missing
• is related to: SOLR-3399 distribute/assume log4j logging rather then JUL
• is related to: SOLR-2487 Do not include slf4j-jdk14 jar in WAR
• is related to: SOLR-4129 Solr UI doesn't support log4j
• relates to: SOLR-4768 The Solr war produced by generate-maven-artifacts should not contain logging jars
• relates to: SOLR-4771 Throw a more specific exception when SLF4J logging jars cannot be found on the classpath.
• relates to: SOLR-4766 smoketester to check war files have the same contents