[
https://issues.apache.org/jira/browse/JAMES-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000146#comment-13000146
]
Felix Knecht commented on JAMES-1149:
-------------------------------------
There exists several (but not many) places where the log level is tried to set,
e.g. in org.apache.james.container.spring.provider.log.LogProviderImpl. This is
not possible using slf4j, as this is only a facade. Setting the log level
programmatically would mean to set it directly to the underlaying logging
framework - which ever this may be.
What shall we do in these cases?
IIRC LogProviderImpl is the only class setting log level and not being a
testcase.
> Replace commons-logging with jcl-over-slf4j
> -------------------------------------------
>
> Key: JAMES-1149
> URL: https://issues.apache.org/jira/browse/JAMES-1149
> Project: JAMES Server
> Issue Type: Task
> Affects Versions: 3.0-M2
> Reporter: Norman Maurer
> Assignee: Norman Maurer
> Fix For: 3.0-M3
>
> Attachments: slfj4-imap.patch, slfj4-mailbox.patch
>
>
> During my expirements with OSGI I noticed all the problems when using
> commons-logging which use some classloader magic. I thinkwe should use
> jcl-over-slf4j to replace it to simplify stuff in the future.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
