[
https://jira.jboss.org/jira/browse/SECURITY-135?page=com.atlassian.jira.p...
]
Darran Lofthouse updated SECURITY-135:
--------------------------------------
Summary: Document the Log4j logging hierarchies (was: Log4j logging
hierarchies )
Fix Version/s: 2.0.3.Beta2
Description: Log4j logging hierarchies allow fine grained control of trace logging -
document the message logging. (was: Log4j logging hierarchies should be used to allow
fine grained control of trace logging.)
Document the Log4j logging hierarchies
---------------------------------------
Key: SECURITY-135
URL:
https://jira.jboss.org/jira/browse/SECURITY-135
Project: JBoss Security and Identity Management
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Negotiation
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 2.0.3.Beta2
Log4j logging hierarchies allow fine grained control of trace logging - document the
message logging.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira