[
https://issues.apache.org/jira/browse/SLING-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-536.
-----------------------------------
Resolution: Fixed
Fix Version/s: Commons Log 2.0.2
This problem has already been fixed in Rev. 668165, I updated the respective
svn log message referring to this issue.
Marking as fixed in the correct version Rev 668165 is part of.
> Log configuration fails with ConfigurationException if log level
> configuration is missing
> -----------------------------------------------------------------------------------------
>
> Key: SLING-536
> URL: https://issues.apache.org/jira/browse/SLING-536
> Project: Sling
> Issue Type: Bug
> Components: Commons Log
> Affects Versions: Commons Log 2.0.2
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Commons Log 2.0.2
>
>
> Currently configuraiton of a logger fails if the log level configuration
> setting is missing. The assumption was that a log level must be provided to
> clearly indicate the logging level required. This is probably true in the
> general case. However, when starting the commons/log bundle in an OSGi
> framework where the global log level is not set by a system property, the log
> level should be properly defaulted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
