You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Thomas Andraschko (JIRA)" <ji...@apache.org> on 2015/07/02 11:39:04 UTC
[jira] [Closed] (DELTASPIKE-944) Logging DeltaSpike to slf4j
instead of JUL
[ https://issues.apache.org/jira/browse/DELTASPIKE-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Andraschko closed DELTASPIKE-944.
----------------------------------------
Resolution: Duplicate
> Logging DeltaSpike to slf4j instead of JUL
> ------------------------------------------
>
> Key: DELTASPIKE-944
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-944
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.4.1
> Reporter: Grzegorz Demecki
> Priority: Minor
> Labels: features
>
> Now DeltaSpike unfortunately logs messages via JUL (java.util.logging.Logger) thus it's not possible in easy way to redirect them to SLF4J. "In easy" way I mean placing on the application classpath {{jul-to-slf4j.jar}} bridge.
> The reason is that the _jul-to-slf4j_ bridge cannot replace classes in the java.util.logging package to do the redirection statically.
> IMHO: it would be nice, if DeltaSpike would use _slf4j_ api as its core logging library. What do you think?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)