[
https://issues.apache.org/jira/browse/JCS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103742#comment-14103742
]
Romain Manni-Bucau commented on JCS-122:
----------------------------------------
that's why it needs to be pluggable (that's 2 small classes). slf4j is broken
in hierarchic classloaders. JUL too but is adapted in containers (Tomcat,
TomEE, JBoss...) to work.
In all cases I think this task will go for 2.1.
> rework logging?
> ---------------
>
> Key: JCS-122
> URL: https://issues.apache.org/jira/browse/JCS-122
> Project: Commons JCS
> Issue Type: Improvement
> Reporter: Romain Manni-Bucau
> Fix For: jcs-2.0.0
>
>
> currently JCS relies on [logging]
> Would be great to get rid of this dependency.
> Solutions I see:
> 1) use JUL (with extensibility like in
> http://svn.apache.org/repos/asf/tomee/tomee/trunk/container/openejb-core/src/main/java/org/apache/openejb/log/logger/)
> 2) write a little factory with a jcs.Logger to be able to switch
> Goal is to be able to adapt to frameworks and users. Guess first will be
> often JUL (TomEE), second SLF4J, [logging]...
> I'm for 1)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
