DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44219>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44219
Summary: 'WARNING' for a log level is silently ignored/changed to
DEBUG
Product: Log4j
Version: 1.2
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Configurator
AssignedTo: log4j-dev@logging.apache.org
ReportedBy: arobert@cogsci.ucsd.edu
When configuring a category, a statement like
log4j.category.foo=WARNING
(instead of ...=WARN)
will elicit no error but simply cause a silent setting to DEBUG instead.
The prevailing context is ignored. E.g., debug output like so:
log4j: Parsing for [foo] with value=[WARNING].
log4j: Level token is [WARNING].
log4j: Category foo set to DEBUG
The behavior should be:
if an unknown logging level token is encountered, complain about it, loudly.
And default to the current context's level, not DEBUG.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
|