[
https://issues.apache.org/jira/browse/JSPWIKI-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642547#action_12642547
]
Janne Jalkanen commented on JSPWIKI-376:
----------------------------------------
Yeah, that's what you get when you have multiple logging packages, all
incompatible, and all changing and/or abandoned, with the one that is a default
is nigh useless.
A lot of projects (like Stripes) therefore use their own logging abstraction so
that people can rewrite it if they want to.
Another possibility might be to switch to java.util.logging and simply get rid
of all logging libraries. But no, we can't do it because we have library
dependencies to all sorts of strange logging libraries...
It's extremely frustrating. With all my other projects, I'm just using the
java builtin logging. It may suck, but at least *I* won't be the one bringing
in a dumb dependency to a logging library.
> 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.
