[jira] [Commented] (JCS-122) rework logging?
[ https://issues.apache.org/jira/browse/JCS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103843#comment-14103843 ] Sebb commented on JCS-122: -- Logging discussions belong on the dev mailing list. > 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)
[jira] [Commented] (JCS-122) rework logging?
[ https://issues.apache.org/jira/browse/JCS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103819#comment-14103819 ] Gary Gregory commented on JCS-122: -- I vote for log4j 2, which you can redirect to other frameworks if desired. > 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)
[jira] [Commented] (JCS-122) rework logging?
[ https://issues.apache.org/jira/browse/JCS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103816#comment-14103816 ] Romain Manni-Bucau commented on JCS-122: Guess it was a bulk update to force us to take attention to it. Not a show stopper (I'll send my feedback tonight normally on open issues) > 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)
[jira] [Commented] (JCS-122) rework logging?
[ https://issues.apache.org/jira/browse/JCS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103808#comment-14103808 ] Yogesh Rao commented on JCS-122: You might have missed looing at the fix version updated above recently :-) This looks to be part of the current release unless changed. > 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)
[jira] [Commented] (JCS-122) rework logging?
[ https://issues.apache.org/jira/browse/JCS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103771#comment-14103771 ] Romain Manni-Bucau commented on JCS-122: Exactly, it does nothing with classloaders (as [logging]) so if you have slf4j in the container and the app it is really a nightmare for the app if the container doesn't help. TomEE helps app to work as expected but it is smoother with JUL since it is built it and integrated. Logging thread are infinite and the need is just trivial - all EE libs of Apache have their thin layer to solve it - so not sure that's the moment (we want to release) to start it now. > 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)
[jira] [Commented] (JCS-122) rework logging?
[ https://issues.apache.org/jira/browse/JCS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103745#comment-14103745 ] Yogesh Rao commented on JCS-122: not that i have come across any CL issue with SLF4J. from what i knew it didnt use or did anything with classloaders. Why dont you take this to ML perhaps someone else can share their thoughts. Regards, -Yogesh > 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)
[jira] [Commented] (JCS-122) rework logging?
[ 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)
[jira] [Commented] (JCS-122) rework logging?
[ https://issues.apache.org/jira/browse/JCS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103701#comment-14103701 ] Yogesh Rao commented on JCS-122: My 2 cents since JCS would be a framework which applications would use (Apart from TomEE) and we cannot dominate the choice of framework there. I would recommend using SLF4J only on the basis of ease of use and its features. My experience with JUL wasnt really that great when i personally tried to use it in an application. > 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)
[jira] [Commented] (JCS-122) rework logging?
[ https://issues.apache.org/jira/browse/JCS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103512#comment-14103512 ] Romain Manni-Bucau commented on JCS-122: Slf4j will work but doesn't help making logging not consistent (if we are able to get rid of sl4j in tomee we would be very happy). Since we own the code we should be able to allow to switch the facade). Nothing preventing a 2.0 BTW. > 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)
[jira] [Commented] (JCS-122) rework logging?
[ https://issues.apache.org/jira/browse/JCS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103379#comment-14103379 ] Yogesh Rao commented on JCS-122: Any particular reason SLF4J wouldnt work in tomee ? Hope i am not missing anything. > 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)
[jira] [Commented] (JCS-122) rework logging?
[ https://issues.apache.org/jira/browse/JCS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987967#comment-13987967 ] Romain Manni-Bucau commented on JCS-122: Yes but reality today is a lot rely on slf4j and the other point is we'll need JUL for tomee without commons-logging. > rework logging? > --- > > Key: JCS-122 > URL: https://issues.apache.org/jira/browse/JCS-122 > Project: Commons JCS > Issue Type: Improvement >Reporter: Romain Manni-Bucau > > 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)
[jira] [Commented] (JCS-122) rework logging?
[ https://issues.apache.org/jira/browse/JCS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987924#comment-13987924 ] Joerg Schaible commented on JCS-122: The intention of [logging] is to enable users to adapt to other frameworks ;-) > rework logging? > --- > > Key: JCS-122 > URL: https://issues.apache.org/jira/browse/JCS-122 > Project: Commons JCS > Issue Type: Improvement >Reporter: Romain Manni-Bucau > > 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)
