[
https://issues.apache.org/jira/browse/JSPWIKI-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642483#action_12642483
]
Ceki Gulcu commented on JSPWIKI-376:
------------------------------------
Hello,
I would like to point out that dependencies on commons-logging can be replaced
by jcl-over-slf4j which is binary compatible with commons-logging 1.1.1 as well
as 1.0.4. Such a move would have all logging go through SLF4J instead of SLF4J
*and* JCL. Moreover, users deploying on Tomcat 5.5.x series would have much
fewer problems when reloading JSPWiki.
Janne, if I could, I would discourage you from writing a facade for SLF4J which
is a facade in itself.
Please ping me on [EMAIL PROTECTED] mailing list if you need help regarding
your planned migration.
HTH,
> 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
>
>
> 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.
