[jboss-jira] [JBoss JIRA] (JBRULES-257) Audit logger to optionally use java.util.logging
[
https://issues.jboss.org/browse/JBRULES-257?page=com.atlassian.jira.plugi...
]
Geoffrey De Smet resolved JBRULES-257.
--------------------------------------
Assignee: Geoffrey De Smet (was: Mark Proctor)
Fix Version/s: 5.5.0.Beta1
(was: FUTURE)
Resolution: Partially Completed
We went for slf4j for now (jboss-logging has shading issues, most frameworks use slf4j and
slf4j has really good logging bridges and maven poms).
To log to java.util.logging, just add a dependency on slf4j-jdk14 and you're done. To
log to commons-logging, add slf4j-jcl. To log to log4j, add slf4j-log4j12. Etcetera.
Anyway, now that's we got rid of the System.out's and System.err's, it should
be doable to bridge that from the slf4j-api's to jboss-logging too.
Audit logger to optionally use java.util.logging
------------------------------------------------
Key: JBRULES-257
URL: https://issues.jboss.org/browse/JBRULES-257
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: drools-core (expert)
Reporter: Michael Neale
Assignee: Geoffrey De Smet
Priority: Optional
Fix For: 5.5.0.Beta1
As we are java 1.4 and up, we can use java.util.logging package to look audit messages.
This means people can use the normal way to configure any sort of logging they dream of,
including viewers, bridges to other logging systems, files, database and so on.
I think logging in JDK is the best choice, even though log4j is better, it would be best
not to add any dependencies to core other then JRE itself.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira