You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Closed) (JIRA)" <ji...@apache.org> on 2012/02/07 15:53:00 UTC
[jira] [Closed] (SLING-2373) Disable default JUL configuration when
using the SLF4J bridge
[ https://issues.apache.org/jira/browse/SLING-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-2373.
-----------------------------------
> Disable default JUL configuration when using the SLF4J bridge
> -------------------------------------------------------------
>
> Key: SLING-2373
> URL: https://issues.apache.org/jira/browse/SLING-2373
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Affects Versions: Commons Log 2.1.2
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Commons Log 3.0.0
>
>
> SLING-2193 added support to redirect JUL logging messages over to SLF4J logging.
> The drawback of the solution is that there is still default configuration read from the JVM platform $JAVA_HOME/lib/logging.properties which causes the JUL ConsoleHandler to be installed.
> Under the assumption that on startup no special logging configuration file is specified with the "java.util.logging.config.file" system property and no logging configuration class is configured with the "java.util.logging.config.class" system property, we should provide a custom configuration class, which does nothing but prevents default configuration from being read.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira