[
https://issues.apache.org/jira/browse/JSPWIKI-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651741#action_12651741
]
Harry Metske commented on JSPWIKI-376:
--------------------------------------
Fixed in 3.0.0-svn-13 revision 721700.
3 new classes in the new package com.ecyrd.jspwiki.log
- LoggerFactory
- Logger (interface)
- LoggerImpl
The LoggerFactory also takes care of registering DynamicMBeans if log4j
is used as the underlying logging implementation.
Log4j remains the default implementation (Stripes still needs it too)
Changes to 34 JSP's
Changes to 135 Java classes
Additions to WEB-INF/lib : slf4j-log4j12-1.5.6.jar,
jul-to-slf4j-1.5.6.jar, jcl-over-slf4j-1.5.6.jar
Removals from .classpath: commons-logging-api.jar, log4j-1.2.14.jar
Additions to .classpath : slf4j-api-1.5.6.jar, jul-to-slf4j-1.5.6.jar
Move log4j config statements from jspwiki.properties to log4j.properties
Changes to build.xml (include org.apache.jspwiki in javadoc gen)
A few other minor changes.
> Move from log4j to slf4j
> ------------------------
>
> Key: JSPWIKI-376
> URL: https://issues.apache.org/jira/browse/JSPWIKI-376
> Project: JSPWiki
> Issue Type: Improvement
> Components: Core & storage
> Reporter: Janne Jalkanen
> Assignee: Harry Metske
> Priority: Minor
> Fix For: 3.0
>
> Attachments: jspwiki-log.odp
>
>
> SLF4J allows far more flexible logging than log4j, and it would allow us to
> get rid of these dumb log4j compatibility problems that sometimes occur. It
> also plays better with other applications, gives the user more power to
> choose how to log his stuff, and is also pretty cool otherwise. The change
> would be relatively trivial, and would probably be largely invisible to the
> users (since we could continue shipping with necessary log4j jars).
> http://www.slf4j.org
> The license is MIT/X11, so that's fine.
> Opinions?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
