You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by "Harry Metske (JIRA)" <ji...@apache.org> on 2008/09/30 18:59:45 UTC

[jira] Updated: (JSPWIKI-376) Move from log4j to slf4j

     [ https://issues.apache.org/jira/browse/JSPWIKI-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Harry Metske updated JSPWIKI-376:
---------------------------------

    Priority: Minor  (was: Major)

Lowering priority because it seems to introduce more potential problems (especially non-core plugins) than it might solve.
Only WebLogic users seem to be affected (not sure if it is true for the current release).
Any feedback from WebLogic users are appreciated, for now let's "freeze" this issue.

> 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.