[
https://issues.apache.org/jira/browse/DIRKRB-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14273668#comment-14273668
]
Emmanuel Lecharny commented on DIRKRB-135:
------------------------------------------
By all means, avoid JUL like plague. This is utter crap.
You will at some point embed the kerberos client or server into some Java
application, and thus will have to use whatever the application uses (whether
it is Log4j, logback or - poor poor boy - JUL). Slf4j is the right approach
here.
> Add logging support in both KDC and KrbClient
> ---------------------------------------------
>
> Key: DIRKRB-135
> URL: https://issues.apache.org/jira/browse/DIRKRB-135
> Project: Directory Kerberos
> Issue Type: Sub-task
> Reporter: Kai Zheng
> Assignee: Emmanuel Lecharny
>
> Currently no logging is done in either KDC server or KrbClient, which is far
> from ideal. We should output meaningful logs help troubleshooting. I guess we
> could leverage slf4j library or just use the Java logging API? The latter
> would be better in the sense that we won't introduce a 3rd party library.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
