[
https://issues.apache.org/jira/browse/DIRKRB-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14362930#comment-14362930
]
Emmanuel Lecharny commented on DIRKRB-135:
------------------------------------------
For the client, I strongly suggest log4j2.0. For the lib, slf4j is, again, the
best choice : you will never know who is going to use the library, and which
(stupid) logger they are going to use.
> 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)
