[
https://issues.apache.org/jira/browse/JSPWIKI-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652438#action_12652438
]
Janne Jalkanen commented on JSPWIKI-376:
----------------------------------------
We don't use markers, so that's fine. As for the API, I think that the varargs
API is a great benefit, as it makes logging code clearer.
I don't understand how that could possibly break the logger selector, or
serialization? It's just a class, and we pass the class name to the slf4j
LoggerFactory directly. Could you please provide concrete examples?
> 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.
