[
https://issues.apache.org/jira/browse/LOGGING-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed LOGGING-120.
-----------------------------------
Resolution: Duplicate
Fix Version/s: (was: 2.0)
> Support kind of isPriorityEnabled / log(Priority) on
> org.apache.commons.logging.Logger
> --------------------------------------------------------------------------------------
>
> Key: LOGGING-120
> URL: https://issues.apache.org/jira/browse/LOGGING-120
> Project: Commons Logging
> Issue Type: Improvement
> Affects Versions: 1.0, 1.0.1, 1.0.3, 1.0.4, 1.1.0, 1.1.1
> Reporter: Maxx
>
> Related to what's be done in library LogKit in class org.apache.log.Logger
> - check
> http://excalibur.apache.org/apidocs/org/apache/log/Logger.html#isPriorityEnabled(org.apache.log.Priority)
> (former log tool in Apache Excalibur...)
> ... as well as what's available in library Log4j in class
> org.apache.log4j.Logger (extending by org.apache.log4j.Category)
> - check
> http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Category.html#isEnabledFor(org.apache.log4j.Priority)
> Would it be possible to support a kind of priority-level test method which
> support a Priority as a param??
> Same thing for the logging method log(Priority, message)
> - check
> http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Category.html#log(org.apache.log4j.Priority,%20java.lang.Object)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
