[
https://issues.apache.org/jira/browse/DELTASPIKE-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14600686#comment-14600686
]
Mark Struberg commented on DELTASPIKE-938:
------------------------------------------
You should find something on the mail archives. Probably on markmail as well.
We had this discussion also for a lot of other framework projects and the main
point is that even the slf4j api is *not* perfectly backward compatible. Thus
we could under some cases create classloader clashes with other versions of a
slf4j-api.jar.
Of coures jul lacks MDC, etc, but at least it doesn't create classpath clashes.
But we use jul only as logging API and you can easily change the logging
backend yourself. The missing MDC also doesn't affect DeltaSpike as anything
you set in an outer level (e.g. a Servlet Filter) will reach all respective
logging backends anyway.
One can easily re-route jul into any other logging backend, and you have to do
this for lots of other frameworks anyway. So there is no real need to use
anything else not to add any additional 3rd party logging dependency. We like
to stay as minimal as we can.
> Enable the use of slf4j for logging without jul2slf4j-bridge
> ------------------------------------------------------------
>
> Key: DELTASPIKE-938
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-938
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.4.1
> Reporter: Jörg Sesterhenn
>
> As a developer i want to use slf4j in my application to be able to choose an
> loggingimplementation at a later point in time.
> deltaspike should suport this without having me use the jul2slf4j brigde wich
> has performance warnings attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
