[
https://issues.apache.org/jira/browse/JSPWIKI-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642257#action_12642257
]
Janne Jalkanen commented on JSPWIKI-376:
----------------------------------------
The point being that at least slf4j allows everyone to choose which logging
package they use... But it's kinda odd to have to carry a generic logging
library and not use it.
Especially since the addition of a bunch of new jars is necessary if we choose
to take the jabsorb library.
BTW, OSCache will go away in 3.0, and be replaced by EhCache (which uses
java.util.logging from 1.6 onwards).
Stripes uses... I don't know what Stripes uses. They seem to fluctuate between
slf4j, commons-logging and log4j.
Jackrabbit uses slf4j. Also a number of other major projects (like Hibernate)
are moving to slf4j...
> 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.
